Nested Trees and History after Splitting

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A. S. Budden wrote:
> Dear all,
> 
> I have just split several parts of my project into separate "library
> modules" that will be used in a number of projects.  However, despite
> the code size being less than 700 k (in one example) and the files
> having only changed about once in the entire project history, the .bzr
> folder is 19 MB.  This is because the 'split' project has taken all of
> the history of the parent project, including the history of all the
> files that have absolutely nothing to do with the library module.
> Given that the modules may be downloaded over the network for lots of
> projects and there may be quite a lot of library modules, this could
> result in quite a long check-out time: if one project requires five of
> the library modules, it'll have to download five copies of the
> original project's history, taking about 100 MB!
> 

If you are using a shared repository then 18 of that 19MB is going to be
redundant and won't be re-downloaded. So you will only download, say, 20MB.

Something to consider when you are thinking about the tradeoffs. If it
is really a copy of the original history, then if it is present in a
shared repo, it won't be downloaded again.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrJ/f0ACgkQJdeBCYSNAANUrACfU7SKxHa9lEuCz6T+qtd4rgzr
724AoLwtw4tYnJITOoBBKV0lAajwWq4Z
=6XrU
-----END PGP SIGNATURE-----