Mercurial vs. Bazaar speedtest clone and log - update: hg 1.1 vs. bzr 1.10
Arne Babenhauserheide
arne_bab at web.de
Mon Dec 15 18:25:19 CST 2008
Am Dienstag 16 Dezember 2008 00:35:06 schrieb Brendan Cully:
> > > 1) Initial cloning:
> > >
> > > time bzr init-repo .
> >
> > Correction. I guess bzr repo comes from bzr-svn conversion,
> > so shared repo format should be explicitly defined as rich-root-pack:
> >
> > time bzr init-repo . --rich-root-pack
>
> How exactly do these shared repositories work? It sounds like they
> would be similar to symlinking .hg into a new directory, a la
> http://www.selenic.com/mercurial/wiki/index.cgi/SharedRepoExtension ?
>
> Can you cleanly delete the history of repository when using the shared
> format?
It looks like the shared repo allows you to have several clones using teh same
repository of changes, but being fully functional.
I assume it is more similar to a main repository and many shallow copies (jus
the last revision) which use the main repository for resolving earlier
changesets.
From the speed with the --hardlink option it looks like it also hardlinks the
workdir files.
Best wishes,
Arne
--
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the
history of free software.
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.
-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20081216/fcff3fd8/attachment.pgp
More information about the Mercurial
mailing list