[Zope-Coders] checkin messages

[Barry A. Warsaw]

>>>>> "JH" == Jeremy Hylton <jeremy@zope.com> writes:

>>>>> "FG" == Florent Guillaume <fg@nuxeo.com> writes:

    FG> If you're reading a bunch of log messages to see what the
    FG> activity was on a piece of code, with the intent of trying to
    FG> see what exactly was impacted, it's not practical to
    FG> constantly refer to an external source of information (go to
    FG> the collector) or go back and forth between branches to find
    FG> out what the checkin message was for the changes to the trunk.

    JH> I agree!  I think it's helpful to include at least a brief
    JH> summary of the changes made on the other branch when doing a
    JH> merge.

Don't forget, checkins will also be read via cvs log years from now.
When you're searching for the patch that changed the foobar widget,
you're going to /really/ appreciate log messages that were written
with care and sufficient detail.

-Barry