Ben Collins-Sussman wrote:
>>This is what we're talking about: when using a working copy path, the
>>cat command works as if the wc revision is used as a peg revision. But
>>when using a repo URL, no peg revision (like HEAD) is used.
>
> Sorry for not reading the whole thread, Stefan. You are correct.
> svn_client_cat() treats a wc-path differently than a URL, exactly as you
> describe, in terms of choosing a 'peg' for following history. I think
> we probably ought to put this in the docstring for svn_client_cat.
Sorry for the delay (lunchtime).
What I don't quite understand is why svn_client_cat() uses a peg for a
working copy path but no peg for repository urls?
I guess this would require a new API function
svn_client_cat_peg()
or something like that so that a client can specify the peg revision to
use (like svn_client_merge_peg() and svn_client_diff_peg() ).
Don't know how hard it would be to implement that though, but I think it
would be worth it.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 27 18:40:22 2004