On Nov 19, 2005, at 11:46, Peter Herth wrote:
> On 11/19/05, Michael Witham <email@example.com> wrote:
>> Is there a reason that you are avoiding this setup?
> Unfortunately, checking out all modules is not an option. First of
> all, there are just to many of them, second, I might not want to have
> the latest version on trunk of all the modules around - depending on
> my task at hand, I might want to be on a branch with certain modules -
> thats the reason I am talking of different modules at all.
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
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.
> So what I really need to be able to do is, to have the subversion
> commands recurse into subdirectories of a directory which is not under
> version control and do their job there, but alltogether as a single
> version control action. Starts sounding like a feature for 1.3...
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.
> As I am talking about repository size, how does subversion scale? As
> CVS only stores on a per-file basis, scaling is not an issue, but how
> is it with subversion, any parts which grow faster than the number of
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
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Nov 19 19:37:32 2005