Re: ancestor path / revision
Branko =?ISO-8859-2?Q?=C8ibej?= <email@example.com> writes:
> > I guess I don't see the problem. Can you give a scenario?
> $ svn checkout http://foo/bar
> A bar
> A bar/baz
> A bar/baz/bzz
> A bar/baz/bzz/a.c
> $ cd bar/baz/bzz
> $ svn copy a.c b.c
> If "bar/baz/bzz" doesn't know the whole path, you have to climb up the
> working copy until you find a directory that does. And that means you
> can't copy a subtree of the working copy and use it somewhere else,
> because it isn't self-contained.
> On the other hand, I may be plain stupid and am missing something obvious.
Well, I don't know about "obvious", but you should be comforted to
know that every directory knows its own absolute ancestry path (see
the dir's own entry in bar/baz/bzz/SVN/entries). That's where it gets
the information; it doesn't have to walk up any trees.
Received on Sat Oct 21 14:36:17 2006
This is an archived mail posted to the Subversion Dev