Re: Best practices log messages early in development

Martin J. Stumpf wrote:
> What do you guys do to make the log really helpful on large projects?

What I sometimes do early on is to just do the mods, an then "at the end
of the day", do an
svn diff | less

And see what actually changed. Typically, there is one major change and
other minor ones. The diff often reminds me of things I forgot I did! :-D

First I try to identify the files that only got one change and that can
be comitted first reducing the number of changes in my changeset.

Then I often do a compound log message like this:
-----------------------------
* Large-modified foo chaning bar to cheese

* Modified X minor

* Enhanced gibberish to include gable.
-----------------------------

In essense, we're already in a messy situation because several
modifications have happened all at once, often in the same files. If I
do one compound log message that mentions all the modifications, at
least later this fundamentally messy situation is documented.

Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 17 00:40:57 2005