[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: pre-commit hook newbie: enforcing ChangeLog updates

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Fri, 22 Aug 2008 12:16:36 -0500

On Aug 22, 2008, at 11:40, Janek Kozicki wrote:

> Quinn Taylor said: (by the date of Fri, 22 Aug 2008 07:27:02
> -0600)
>> I can at least understand the
>> desire to require that this be updated to avoid having someone dig
>> through the logs and summarize what has changed right before a
>> release.
> this is exactly the case. I had to dig through 200 svn log entries
> and filter out the most important stuff for "release news".
> Perhaps I will set the ChangeLog update limit to 10 or 20 commits. So
> those 200 svn log entries would be summarized in 10 or 20 ChangeLog
> entries. From those entries it would be much easier for me to prepare
> "release news". And also I will learn about what important others
> have done :)

If you just want to keep track of what others in your team are
committing -- and that's a good thing to be keeping track of -- it's
useful to set up a commit mailing list, to which an automated email
is sent after every commit, with the diff of the commit. This way
changes can be reviewed and critiqued immediately.

> Also it has to be on per-user basis, because each person in the team
> is working on separate parts of the code and they know the best what
> they have done.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-22 19:16:58 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.