Hi Toralf, By "what has changed" do you mean the list of modified files or a brief description / explanation of what has changed?
For those of us who use a GUI interface to GIT like SourceTree, it is _very_ helpful for the GIT commit message to start with a brief description of _what_ has changed. SourceTree (which I highly recommend) presents a list of commits as one line each, with the first part of the commit message shown for each. This allows us very quickly to see what has changed with each commit without needing to examine each one individually. 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. Cheers, --Charlie On May 28, 2013, at 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, > especially comments shouldn't tell what was changed but why a change was > made, or ? > > > -- > MfG/Sincerely > Toralf Förster > pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
