[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-18 04:18:34 CEST

> If you want a 1 to 1 file to commit comment mapping, check your files in 1
> at a time and you will get the desired output. However, you loose the
> change set functionality by checking in 1 file at a time.

We want it both ways. Clearly the CVS way is not good enough (in Emacs,
we supplement it with a ChangeLog file to make up for it. With subversion
we could just use `svn log .' instead).

> OR *untried* write a commit hook that parses a formatted commit message
> and adds a revision level property of "comment" to each file. Then you
> could list the comment properties for the file in question.

I don't think we need to go that far. As I pointed out, you can
simply use a formatting convention and parse the output of `svn log'.
As a matter of fact, the subversion repository seems to follow such
a convention.
This has the advantage that the comment can be changed later on,
contrary to properties.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 18 04:19:41 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.