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

Re: Possible way to support $Log$

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-04-20 21:24:01 CEST

> Mark Phippard wrote:
> [snip]
> > said, the best argument I have seen for it was by someone who said
> > primarily work disconnected from the repository and need the
> > so that they can do as much research as possible without having a
> > repository connection. With that in mind, would it be possible to
> > an option to store the log information in the WC and then either make
> > some new or existing svn commands that could look at this information?

> You mean something like
> svn log > logfile.txt
> ?
> /me thinking:
> Subversion could do that automatically when doing checkouts/updates and
> store this information somewhere (e.g. in the top folder of the wc, in
> the .svn dir).
> Then an additional option to 'svn log' (e.g. 'svn log --no-net') would
> simply show that file with all the logs in it.
> Sounds like a good feature to me - but that's just me.

My idea is probably half-baked because I do not use the feature and am
also a Subversion newbie.

I was thinking that there would be a log-base folder like the prop-base
folder with a file for each file that had the equivalent of what a fully
expanded $Log$ would have. That way it would be easy to see the change
history for a specific file, which seems to be the issue in wanting this
keyword. There could be a switch or something on the svn command(s) that
would normally get this from the repository to instead get it from the WC.

Having one file with the complete history for a project is nice for some
problems, but not nice for others, such as wanting to see the changes for
a specific file.

Received on Tue Apr 20 21:26:09 2004

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.