Brief article on benchmarks of Python repository with leading DVCSen
Nicholas Allen
nick.allen at onlinehome.de
Thu Feb 12 09:23:07 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stephen J. Turnbull wrote:
> Vincent Ladeuil writes:
>
> > >> Not the primary storage location for revisions. Revisions
> > >> would still be stored in the branches or the shared
> > >> repositories as usual.
> >
> > aaron> If revisions are stored in the branches, why would you
> > aaron> store them in the cache?
> >
> > To avoid downloading them when branching outside of a shared
> > repo.
>
> But you'd still be in a shared repo, you'd just *call* it "cache"!
Like I said the cache is not the same as a shared repository. The cache
is per user (not any directory structure). It is also self pruning.
Unlike a shared repository it is always safe to remove or empty the
cache. The worst that can happen is that there is slower performance
when branching remote locations.
Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkmT6nsACgkQ1+i51gqqEGkvwQCaAkjQ/4FGl6RLQNLUCRcnp9YU
1woAoJdmrhfNRt4NnLrnJ4eNWIRQWnKv
=KY65
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list