[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: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 30 Mar 2010 15:21:45 -0400

Vincent Lefevre wrote:
> On 2010-03-30 12:12:59 -0400, C. Michael Pilato wrote:
>> Interactions in the working copy with the path some/file.c only make sense
>> if there is actually such a path in the working copy. If some/file.c is
>> deleted in r51, then either it isn't in your working copy (because you've
>> updated past r50) or it is, at r50 or earlier. If it is, you run 'svn cat
>> some/file.c' as usual. If it isn't, then the path 'some/file.c' has no
>> meaning anyway, so it falls to you to spelunk history and tell Subversion
>> more precisely what object you're talking about.
> I want a simple way to say: consider the current directory at r50
> (walking back through the history) and the object some/file.c in
> it at the same revision.

I'm sure you're not alone, but Subversion doesn't cleanly provide such a way

$ svn cat `svn info some/ -r50 | grep ^URL: | cut -c 6-`/file.c_at_50


C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2010-03-30 21:22:17 CEST

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