'update' history tracing?

Someone in IRC did this:

    $ svn checkout http://svn.collab.net/repos/svn/tags/1.1.1
    $ cd 1.1.1
    $ svn update -r10000

A cryptic error is returned, probably because the tag doesn't exist in
r10000.

The user was surprised, because he expected history to be traced. And
after thinking about it for a moment, it seemed pretty logical to me
too.

I mean, why aren't peg-objects coming into play here? I imagine that
under the hood, the client should be running:

    $ svn update -r10000 wctarget@BASE

...tracing 'wctarget@BASE' back to 'newlocation@r10000', then doing an
RA->do_switch() operation to the new URL and rev.

I guess this means that running 'svn up -rX' could potentially change
the urls in your working copy, but that seems ok to me. That's what
history-tracing is all about.

What do others think? Should we add it to issue #1093?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 11 22:48:52 2004