Troy Curtis Jr wrote:
> On 11/3/07, Julian Foad <julianfoad@btopenworld.com> wrote:
>
[...]
>>One could be tempted to say things like, if there's a local path involved in
>>the command, then look for the repository of that as well or instead of the
>>current directory. I suspect that way would lie madness but maybe current
>>working directory isn't the only possible rule.
>
> Or the other thing I thought was use the root URL of the full url
> found earlier in the command-line so that:
> svn cp file://some/repo/trunk/ ^/branches/1.x
> would work, but again, madness :).
:-)
>>It would be interesting to show a set of typical usage scenarios - tagging,
>>branching, merging, listing contents, etc. - with the exact realistic commands.
>
> I have implemented the relative urls in my own tree for everything
> (that makes sense) except switch, and have already found them very
> useful for 'svn ls', 'svn cp' and 'svn info' as I run through some
> manual tests. In fact, I really missed it today at work where I don't
> have my changes!
>
>
[...]
> If I can get the cmdline merge test figured out, I will be hopefully
> be submitting a fully implemented, documented, and the corresponding
> tests for the 'svn merge' case.
Cool! Good work.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 7 00:02:29 2007