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

RE: Feature request: Keyword $Rev$ with a twist

From: Mats Nilsson <mats.nilsson_at_xware.se>
Date: 2002-07-31 20:56:10 CEST

sussman@collab.net [mailto:sussman@collab.net] writes:
> But then also, what if
> somebody checks out the latest fs-convert-2092 branch from HEAD?
> Well, then you'll have a "2092 branch binary" that claims to be at
> revision 2805 or something... big confusion.

It wouldn't be used alone, of course.

I think the following is pretty clear.
        $WorkingRev: 2805 $
        $URL: http://svn.collab.net/branches/fs-convert-2092 $

That part of the issue is more related to giving branches meaningful names.
In this case fs-convert-2092 means something for those involved.

> But hey, if others want to use a $WorkingRev$ keyword for whatever
> reason, then I'm +0 on adding that feature.

I'd like to have it, but there may be other useful variants. Dave Cridland
was on to something when he spoke about the containing directory's Last
Change Revision. Maybe this can be captured as a keyword?

        $ContainingDirectoryLastChangeRev: 2805 $
or rather
        $RelativePathLastChangeRev ../..: 2805 $


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 31 20:58:59 2002

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.