> Can't help you with #1; if you won't arrange your repository this way
> and check out the entire trunk, then you cannot do what you're asking
> for.
The arrangement of the repository would be no problem, but as I wrote,
checking out the whole repository is not possible.
>
> To #2, there's no reason you can't check out the entire trunk, then
> switch, say, module-B to a particular branch. That's what "svn
> switch" is for.
Interesting that it is possible to operate, when the subdirectories
are on arbitrary parts of the repository (since branches are only
files in another directory) but not on "incomplete" checkouts.
> I thought I heard that this feature existed before Subversion 1.0 but
> that it was removed for some reason. But I cannot find the email in
> which I thought I was told that; all I can find is emails like this,
> which just show that it doesn't work.
>
> http://svn.haxx.se/dev/archive-2002-07/0107.shtml
>
>
> I don't think there are any scalabitily issues that you need to worry
> about. Subversion stores revisions, not files, so as soon as you're
> committing more than one file at a time, sounds like Subversion is
> going to be having fewer things to store than CVS. Big projects like
> Apache are already using Subversion so it must work ok even for large
> projects.
That sounds good, though I would have to check how big the Apache
project is in comparison :).
Thanks for your answer,
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 19 21:42:16 2005