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/fil...@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 <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
