Just so long as the git-committer message is hooked up properly to the trac timeline and revision log, please. In the past, that's been the biggest problem - from my point of view - with non-atomic commits: something gets changed, and even if there's a reference way down the checkin_notes file, it can't be seen in the one-line summaries.
>________________________________ >From: Oliver Bock <[email protected]> >To: [email protected] >Sent: Thursday, 25 October 2012, 13:10 >Subject: Re: [boinc_dev] Git commits: message formatting and atomicity > >On 10/25/12 14:02 , Oliver Bock wrote: >> Have a look at your merges so far: 4f422d5, e273e4f, 22fe7a0. All of >> them had a merge conflict in that file -- which is to be expected as you >> all make your updates at the top of the file. > >Well, bottom, even worse. >_______________________________________________ >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.
