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

Re: CVS $Log$ equivalent in Subversion?

From: Bob Bradley <bob_at_chaoticsoftware.com>
Date: 2004-03-09 09:37:09 CET

On 3/8/04 8:29 PM, "C. Michael Pilato" <cmpilato@collab.net> wrote:

> Rephrased, if for some weird reason CVS's all over the world magically
> stopped supporting the $Log$ command, would this be the end of the
> universe for you?
> If so, why? I'd be interested in hearing a good
> solid reason for support of this $Log$ feature.

We rely on having commit messages in each file for searching, change
tracking across branches and merges that aren't always linked, etc. Having
to go to the server to get this information by invoking log commands each
time is slow, tedious, and sometimes impossible (e.g. when on a plane or
otherwise without net access or when coming from another repository). Others
also get drops of the source without repository access so they would have no
means to get the log messages. The log messages could be extracted as part
of the release process as previously suggested, but that would either result
in one huge file with all the commit messages (unwieldy), we'd have to have
two files for each real file: the real file and the commit message file,
which is also problematic, or we have to write some script to insert them in
all files manually (also problematic).

> After all, Subversion
> should have a few more years left in it to grow new important
> features. :-)

I hope so and it would be great to move to Subversion as it has a ton of
great features I'd like to use, but unfortunately, without certain features
we rely heavily on, it's just not feasible to switch yet. I don't really
understand the objection to $Log$ support. It's an optional keyword that
nobody has to use unless they want to. If managed properly, it doesn't have
to cause any problems. I think the keywords that are already supported by
Subversion (e.g. $Id$ which almost guarantees a conflict by most diff tools)
are much more problematic than $Log (at least for me).

It seems to me that people have chosen to manage sources in a way that
conflicts with using $Log$ and because of this, it has been decreed that
$Log$ is evil and should be banned. Others, like myself, manage sources in
ways that work well with $Log$ (and conversely don't work well with other
keywords like $Id$). I think both ways are equally valid and the individual
developer should be given the choice rather than have a particular style
chosen for them.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 9 21:21:57 2004

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