Re: Generating a daily changelog for /trunk and /branches/1.3.x

Kevin Greiner wrote:
> On 3/12/06, *Stefan Küng* <tortoisesvn@gmail.com
> <mailto:tortoisesvn@gmail.com>> wrote:
>
> I've set it up on my own nightly build machine. I'm just not quite sure
> if that changelog will be of any real use for the 1.3.x branch: the log
> messages there aren't really helpful :)
>
>
>
> At my company, I'm considering installing svn2cl with the output emailed
> weekly to the entire dev list just to encourage good commit messages.
>
> Philosophically, I wonder if there is a contradiction between saying
> "commit early and often" and "write good commit messages". Sometimes I
> commit changes so small, they are trivial to comment ( e.g., "reworded
> comment to make sense"). Does raising expectations for descriptive
> commit message mean devs will commit less often?

I don't think so, once they're 'trained' to write log messages.

The log messages on the branch which I was referring to are not helpful
in a changelog of the branch only because they're usually like this:
merge revision xxxx and yyyy from trunk.
So they only make sense if you have the log from trunk too.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org