On 05/29/2013 01:08 AM, Charlie Fenton wrote:
I agree with Jord that 'quick updates', or 'quick fixes' is not helpful, but
I also don't want to see empty commit messages. I feel that _every_ commit
should have a commit message briefly describing what was changed and why.
Yeah - I was just
Hi Toralf,
Yeah - I was just grumbling about a commit with the only message
Include cmath instead of math.h various places
nothing else - and of course gitk shows for a dozen of files such a
change. Every ?!%%$$ user can see the diff using gitk - so important
IMO is just a short
It would be sometimes helpful for 3rd party
testers/reviewers/people_which_are_just_interested if the git comments
would be more descriptive or completely empty to not waste space,
especially comments shouldn't tell what was changed but why a change was
made, or ?
--
MfG/Sincerely
Toralf
Please give examples of non-descriptive comments.
-- David
On 28-May-2013 1:56 PM, Toralf Förster wrote:
It would be sometimes helpful for 3rd party
testers/reviewers/people_which_are_just_interested if the git comments
would be more descriptive or completely empty to not waste space,
I'd rather that there'd be a more uniform use the prefixes. That
everyone use the same prefix, so that those of us keeping change logs
can see a bit easier what goes where.
Now there's a couple of entries that say client, but are android. Or
some entries that have no prefix whatsoever, and only by
