Bazaar repository size benchmarks

John Arbash Meinel john at
Tue Jun 3 23:13:03 BST 2008

Hash: SHA1

Christophe TROESTLER wrote:
| On Tue, 03 Jun 2008 11:09:54 -0400, Stefan Monnier wrote:
|>>> You need to be using an editor that breaks hard-links on save to use this
|>>> feature safely. Or a more manual process, of course.
|>> It would be really nice if some tips on how to achieve that were added
|>> to (if possible, only for files under
|>> bzr so as not to change emacs 22 default behavior).
|> Such things could also be added directly to Emacs's vc-bzr.el (or vc.el
|> if it's not specific to Bzr).  Although my opinion is that using
|> hardlinks like that is just a bad idea.
| I agree that hard links are a bad idea (high risk) but avoiding the
| replication of an entire working tree to develop a feature (which may
| modify only a few files) is also good to have.
| What about the following scheme: have a repository with all your
| branches but --no-trees and have a directory where one does
| --lightweight checkouts?  To be convenient one certainly would like a
| --replace (or such) option so that the directory discards the old
| checkout and replaces it with the new one (and choke if there are
| uncommited changes).  Or maybe a plugin could support this well?
| My 0.02€,
| ChriS

The '--replace' is implemented with 'bzr switch', though it doesn't choke for
uncommitted changes (so that you can switch and commit the changes somewhere
else). It certainly wouldn't be hard to implement that.

I'm currently trying out that workflow. What I miss the most is seeing the name
of the branch I'm working in, in my command prompt. (I always see ~/bzr/work
now, rather than ~/bzr/1.6-dev/feature-foo, but I can change my prompt to
include 'bzr nick' if I really end up missing it.)


Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla -


More information about the bazaar mailing list