Julian Foad <julianfoad@btopenworld.com> writes:
> Ben Collins-Sussman wrote:
> > Julian Foad <julianfoad@btopenworld.com> writes:
> >
> >>What is the reason for this bit of code that forbids "-rCOMMITTED"?
> >>It does not forbid "-rPREV".
> > Huh... I'm not sure why we forbid COMMITTED, but not PREV. They're
> > very similar revision keywords. cmpilato will be back from vacation
> > in a couple of days; let's see
> > what he says. He rewrote all of this code while *I* was on vacation
> > last month. :-)
>
> $ ping cmpilato
>
> (re. the lines leading up to the message "do_diff: COMMITTED nomenclature not supported" in subversion/libsvn_client/diff.c)
>
> I propose to delete those five lines, thus enabling "COMMITTED" to be used.
Thus enabling COMMITTED to be used incorrectly, you mean.
What is the expected behavior when COMMITTED is used in conjunction
with a URL input path? Does it peg one particular revision number for
whole tree, or does it get effectively re-evaluated for each path
(like BASE and WORKING do)?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 17 05:00:08 2003