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

Re: Logging granularity

From: Stefan Monnier <monnier+gmane.comp.version-control.subversion.devel/news/_at_rum.cs.yale.edu>
Date: 2003-05-15 23:47:50 CEST

>>>>> "Branko" == Branko Čibej <brane@xbc.nu> writes:
> On the other hand, it's quite easy to write a wrapper script around "svn
> log" that filters the log output like this, and you can then educate
> your users about the correct log message format. This seems like a
> site-specific thing that can easily use a site-specific solution,
> without touching Subversion code at all.

Of course, what would be neat is if `svn' offered a way to hook
such a wrapper into `svn' directly so that users can keep using
`svn commit' and `svn log' rather than having to use `svn-commit'
and `svn-log' (which GUI front ends will not know to do).

It might be a good idea to provide sample such scripts.
Being an Emacs user, I'd imagine a format similar to the ChangeLog
format (so that converting `svn log' to ChangeLog is real easy),
which also happens to be similar to what is used in subversion's
own repository. I.e.

        <global comment>
        * <file1> <comment1>
        * <file2> <comment2>

The only tricky part of the wrappers will be to adjust the filenames
to account for the fact that they are relative to the current
directory. This will probably require adding somewhere in the log
entry the full path (from repository root) of the current directory.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 15 23:52:14 2003

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

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