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 opening the whole commit and checking what files were they changed in, can we determine if it was a change for the change log or not.
Like these: android API client condor db-purge MGR scheduler server web Now one person does Client, the other client, the third nothing. Or one person uses mgr, the other MGR, then a third says Manager, etc. It would also be nice if all sentences ended with a full stop, but perhaps that's just wishful thinking. :-) As for 'non-descriptive comments', we all hate the 'quick updates', or 'quick fixes'. I just take it that sometimes those cannot be helped. On Tue, May 28, 2013 at 10:59 PM, David Anderson <[email protected]> wrote: > 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, >> especially comments shouldn't tell what was changed but why a change was >> made, or ? >> >> > _______________________________________________ > 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. -- -- Jord van der Elst. _______________________________________________ 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.
