"digest" tag in commit messages

[Danny Allen]

I've just written a reply:

-----------------------

Hi John,
Yes! This is something we have been discussing for quite a while now, and its something that wouldn't be difficult to implement on my end, as long as tags are consistent.

I propose that the tags always be uppercase, so in this case:

DIGEST (this could be the generic tag)
FEATURE (self-explanatory)
BUG:99999

For bugs, this is really important: currently, people use lots of different formats like "BUG:99999" (good), "Bug: 99999", even "bug 99999" - you can imagine how hard it is to pull this one out of a body of text!

Can we enforce one standard and shame the repeat offenders?

Send me an email at danny at commit-digest.org when you've got a final proposal!

Cheers,
Danny


----- Original Message -----
From: "Marco Krohn" <marco.krohn at googlemail.com>
To: "digest" <digest at kde.org>
Cc: "Danny Allen" <danny at commit-digest.org>
Sent: Tuesday, 22 February, 2011 11:27:48 PM
Subject: "digest" tag in commit messages

Hi all, 


Please see the comments for the latest Commit-Digest 


http://dot.kde.org/2011/02/21/kde-commit-digest-30th-january-2011 


I suggested to Gilles to add a "[digest]" tag in the commit message if a developer thinks that a commit should be included in the Commit-Digest. He seems to like the idea. If you agree we should look for this specific tag during the review process and maybe Danny can implement an additional icon if such a tag is found!? Alternatively we could use "DIGEST" as tag, which would be more in line with the other tags (BUG, FEATURE) in use (as suggested by Odysseus). 


Best regards, 
Marco