On 2010-03-29 12:36:11 -0400, C. Michael Pilato wrote: > I was about to post that one place where there might be a lack of > documentation is not so much in understanding what the peg revision means, > but in understanding the "working copy path" -> "peg path" translation. The > peg path algorithm works in repository path/rev space only. So any time a > working copy path needs to be fed into that algorithm, it must be translated > into a repository path (which on the client side comes in the form of a > repository URL). To make that transformation, Subversion will resolve any > working copy target path into its URL *as recorded in the working copy*, > then use that as the path portion of the (path, peg-rev) input to the peg > revision algorithm. > > And yes, as Greg points out, when a working copy object has no URL (because > it is new and scheduled for addition), then the URL is probably constructed > by tacking the object's basename onto the parent's URL.
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. -- Vincent Lefèvre <vinc...@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)
