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

Re: description of Peg Revision Algorithm is incomplete

From: Vincent Lefevre <vincent-svn_at_vinc17.net>
Date: Tue, 30 Mar 2010 23:07:25 +0200

On 2010-03-30 21:36:27 +0200, Stefan Sperling wrote:
> Maybe we could some day extend peg revision syntax so that every
> component of a path can be pegged?
>
> So what Vincent wants would be something like this:
>
> $ svn cat ._at_50/some/file.c

I almost proposed this, but the syntax would not be this one. Indeed,
if I understand correctly, ._at_50 means the URL of the current directory
at revision 50, while I want the current directory at revision 50,
taking into account the possible renamings (i.e. not a peg-rev on ".",
but -r50 on "."). Now, one could imagine a slightly different syntax,
e.g.

  svn cat .@:50/some/file.c

where ":" means that one follows the history (like with -r).

Actually, I don't think that peg revisions (i.e. without following the
history) make much sense on objects relative to the current directory
(unless its URL has not changed since the peg-rev).

> And make svn treat a double-@ as actual @:
>
> $ ls
> dir_at_example.com
> $ svn cat dir@@example.com/file.c

Yes.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
Received on 2010-03-30 23:07:53 CEST

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