[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Understanding clones and the file system

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-08-02 18:02:40 CEST

<peter.westlake@arm.com> writes:

> > $ svn checkout http://foo.com/svn/repo/trunk
> >
> > ...assuming that there are no other siblings of "paint" in trunk.
>
>
> Wrong assumption :-)
>
> I'm after the case where there *are* siblings, but I don't want them all.

I don't think that's possible. If you check out a directory, then you
get its contents. From a use-case point of view, it's nice to say "I
want to checkout a directory and only get part of its contents." But
from a theoretical point of view, this is not a happy situation.
Remember that directories are versioned. Either you have revision 5
of 'trunk' or you don't.

Of course, you could checkout all of 'trunk' and then afterwards
update all the unwanted children to revision 0. Or maybe we could
come up with a new 'svn co' syntax for doing this automatically.

> I would love to contribute to this. Even if we choose a different
> source control system, I shall be thinking about Subversion in my
> spare time, and I would be happy to work out use cases and examples.
> The chance to influence the UI is a wonderful opportunity too.

Excellent!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:34 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.