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

Re: SVN properties keywords

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Wed, 14 Jan 2009 20:33:49 -0600

On Jan 14, 2009, at 20:19, Torsten Giebl wrote:

>> But what exactly would you add or change in Subversion?
> I would like to have a svn:keywordseverytime for example.
> Every file that has this property set, will always be updated
> when there is a change in the repository, even when the file itself
> is not changed. So for example an $Id$ or
> $Revision$ in it, will always be up to date. I would call it then
> not $Revision$, but something like $BiggestRevision$ or so.

But as the FAQ entry explains:

"Subversion increments the revision number of the repository as a
whole, so it can't expand any keyword to be that number - it would
have to search and possibly modify every file in your working copy on
every update and commit."

To expand on that, I think it means that on every update and commit,
Subversion would have to look at the svn:keywords property of every
file in your working copy to see if it uses the BiggestRevision
keyword, and if so, replace the revision in that file. That would
probably slow things down drastically as Subversion would have to
read many more prop-base files than before to make this
determination. And this performance issue would affect everybody, not
just those using this new keyword.

Perhaps the working copy redesign for Subversion 2.0, which will
consolidate working copy data in a central place instead of scattered
in lots of .svn directories, will make this a less expensive
operation at which time the topic could be revisited, but I don't
think there's a way to implement this now that would not slow
Subversion down a lot for everybody.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-16 17:51:17 CET

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.