[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 09:31:27 -0400

Vincent Lefevre wrote:
> Couldn't peg-rev be also taken into account to translate a working copy
> object into a URL? This would make sense if the parent directory has
> been renamed: as peg-rev is used to point to some object in the past,
> one should consider what the URL was in the past.

No, because peg revisions aren't about translation. They are about
selection. They are the waypoints or landmarks or some-other-
navigationally-analogous-thing by which Subversion determines which line of
history you are talking about. After -- and only after -- that selection is
made, translation occurs via the operational revision(s).

Nobody should be trying to run 'svn cat some/file.c_at_50' if what they mean is
"follow the history of some/file.c back to r50 and cat the contents there".
 That's just not the correct syntax for invoking the algorithm, and no
amount of wishful thinking will change that. The correct syntax for that
request is 'svn cat some/file.c -r50'.

I'll grant that Subversion does have a sort of pre-translation step there
where it converts working copy paths to URLs, but that step already has
clear rules that perhaps just need some spelling out in the docs.

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

Received on 2010-03-30 15:32:10 CEST

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