On Tue, Feb 26, 2008 at 10:16 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> Also, if you go this route, then you absolutely should allow --revision to
> override the default operative revision (the peg revision) for parity with
> all the other subcommands that implement the peg-revision algorithm. In
> other words, we're back to --revision being the primary way to specify the
> based-on-revision for this propchange, with the typical chain of default
> values for that revision: it defaults to the peg revision's value, which
> defaults to HEAD for URLs and BASE for working copy paths.
Hmm. This doesn't work for me.
The base revision needs to be specified separately from the operative
revision, because the two things might be different. Consider, for
example, if I want to replace the file 'dest' with 'src_at_500'.
svn cp ---replace src_at_500 dest_at_1000
The 'base revision' refers to the target whereas the 'operative
revision' refers to the source. Perhaps we should use the term 'target
revision' to be clear about this difference.
Should the 'target revision' always be the same as the 'target peg
revision'? I think so. I can't think of any useful use case where I
would want to specify a target revision which is different from the
target peg revision. So that's why I agree with Julian.
Cheers,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-26 19:30:06 CET