Jani Monoses jani@iv.ro writes:
So the original WS is 290Megs the one from which I commited the kernel.
The two other WCs (local and ra_svn) after update are both 534M.
Yes, the working copies are roughly twice as big as the original tree
you imported into the repository. That's normal. Every file has a
second cached pristine copy within .svn/text-base/, so that svn can
perform many disconnected operations.
Just to make sure we're talking about the same thing.
The 2 WC-s are twice as big as the first WC and not the kernel tree itself.
So let's say I have a clean tree A. Copy that to WC1 and commit
from there.Now the tree A will have additional .svn metadata which
will increase it's size. So size (A in WC1) size (pristine A)
although comparable. Updated WC2 will have size (A in WC2) about 2
* size (A in WC1) ?Shouldn't they have the same kind of meta info?
So I was asking why the WC's are different size .I can understand
that a WC is bigger than a non revision controlled tree.
If this is what you're seeing, then something is wrong.
All working copies should be the same size.
How did you commit from WC1? Did you run 'svn add' to recursively
schedule the whole tree for addition, then 'svn commit'? Or did you
use 'svn import'? Does WC1 have any .svn/text-base/ files like the
other two WC's?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:25:22 2006