On 11/19/05, Michael Witham <mwitham@yahoo.com> wrote:
> How big are the modules?
>
> Would it matter if you have all the modules checked
> out onto your computer?
>
> Is there a reason that you are avoiding this setup?
> repository/
> branches/
> tags/
> trunk/
> module-A/
> files-of-A
> module-B/
> files-of-B
> module-C/
> files-of-C
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.
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...
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
files?
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 11:49:06 2005