On 1/2/07, Hyrum K. Wright <hyrum_wright@mail.utexas.edu> wrote:
> I'm adding support for peg revision syntax to 'svn copy' and I just want
> to make sure that I've got things straight with regard to peg revisions
> (peg revs), and operational revisions (op revs).
>
> Each source needs both a peg rev, and an op rev, which may be different.
> Depending on which combinations of peg rev and op rev happen several
> scenarios are possible. By my count, there are four possible cases for
> each source:
>
> 1) No peg rev, no op rev
> Example: 'svn cp src dst'
> Peg rev: HEAD
> Op rev: HEAD
>
> 2) No peg rev, op rev
> Example: 'svn cp src dst -r 200'
> Peg rev: 200
> Op rev: 200
I think this second example is wrong. My understanding is that if the
path doesn't have an explicit pegrev (@), then it defaults to HEAD.
Let me generalize: my understanding is that for *any* command:
* URLs pegrevs default to HEAD, unless specified by @N
* wc-path pegrevs default to BASE, unless specified by @N
* operational revs default to pegrev, unless specified by -rN
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 3 04:20:43 2007