Julian Foad <julianfoad@btopenworld.com> writes:
> That sounds sound. Syntax 1 below doesn't allow Z to be specified,
> so, until syntax 1 is extended, this is limited to Z = WC. I would
> guess that this case would most commonly arise in the form "diff
> -rX:HEAD path", when the WC is not quite up to date.
Yep, that was my thinking too.
> We should clarify "restricted to the paths PATH..." with regard to
> that limitation. The current help says "PATHs, if given, are
> relative to OLD-TGT and NEW-TGT and restrict the output to
> differences for those paths." This is still not quite clear; I
> assume it means the union of PATHs that exist under OLD-TGT and
> PATHs that exist under NEW-TGT, with those that are only present on
> one side causing an "added" or "deleted" diff. Or does it mean that
> it is an error if any PATH does not exist on both sides?
It basically means that a diff will be done between each pair of
OLD-TGT/PATH vs. NEW-TGT/PATH. The behavior of each of those diffs
will be exactly the same as if you'd done 'svn diff OLD-TGT/PATH
NEW-TGT/PATH'.
> > None of these forms mix the -rX:Y and the @-syntax because Greg deems
> > that stuff esoteric. For now, I'm willing to lay down and concede
> > that. In my mind, though, the best benefit of that fact is that the
> > command-line parsing code doesn't have a change a lick in order to
> > handle these use cases (though, I think there is one de-unification
> > I'd like to see, not directly related to this topic).
>
> This seems like a nice clean syntax, and it leaves room to add
> support for "@PEG" on the TARGETs of syntax 1 so that deleted items
> can be referenced easily.
That was my thinking, too. If we later need to expose the whole API
-- or if other GUI clients want to do so -- it's available.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 11 02:34:46 2003