On Fri, 29 Oct 2004 22:33:19 +0200, Torsten Curdt <tcurdt@apache.org> wrote:
> Hi there,
>
> it's quite common to have some kind
> of changelog in projects. Currently
> there are two options.
>
> Generating a changelog from a commit
> log or add the changes to a changelog
> file under version control on each commit.
>
> The latter one is quite annoying as
> it's another resource that needs to
> kept in sync and basically takes
> mostly the same information that go
> into the commit message.
You forget the last and most natural solution to use with Subversion:
Since you have a global commit log, you essentially already have your
changelog. If you write a pre-commit hook to scan for the required
items and reject the commit if those are not in the log message, you
can have the output from svn log as your changelog. See the svn log
output for Subversion trunk/.
> So my idea was to use a pre commit
> hook to search the commit message for
> the required information and add
> them to the changelog file ..which
> is under version control.
I believe projects do this to compensate for CVS' lack of a global
commit log. As such this way of thinking is an artifact of (years of)
CVS use. With Subversion you don't need that anymore.
> But this means the pre commit hook
> needs to change the transaction.
>
> Somewhere I read this is not (yet?)
> possible.
>
> What's the status on that?
It's not currently possible and not on any schedule to be addressed.
Most Subversion developers feel that it's not ok for a server to
change a committers contribution.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 29 22:47:00 2004