On Wed, 2009-09-02 at 08:14 -0700, Doug Barton wrote: > That said, for RELENG_8 commits during the freeze re@ did ask in one > of their many messages about commit approvals to paste the complete > commit message in the MFC. So, bad Alfred, no cookie. :)
Just for clarification... We ask that you send your complete *proposed
commit message* in your *approval request*. We didn't say that your
commit message needs to include all of the text from the commit to head.
So, bad Doug, no cookie. :-)
FWIW my preference is, as usual, somewhere in between the two extremes.
Duplicating a lengthy commit message in a merge is overkill but in those
cases a short (one sentence max) summary of what changed being in the
merge commit message is helpful. For example when looking through the
commits for release notes fodder it can help. It also helps people who
take the peer review of commits being done seriously to get the warm
fuzzy feeling that the merge wasn't an accidental mis-merge (by seeing
that the code seems to match the brief description).
--
Ken Smith
- From there to here, from here to | kensm...@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
signature.asc
Description: This is a digitally signed message part
