bazaar performance with single large project and a comparison with?git / mercurial

[Matt Nordhoff]

Stephen J. Turnbull wrote:
> No.  When you do "darcs record", darcs goes into an interactive mode
> where you can choose which hunks will be recorded as part of the
> patch.  So suppose while you were adding a new feature, you also
> notice a couple of typos in comments which should have fixes pushed to
> mainline immediately.  In darcs, you fix them immediately, then you
> record one patch which excludes those hunks, then you record a second
> patch which includes *only* those hunks.
> 
> In git, I approximate this by committing as soon as I see the
> unrelated typo, then committing the typo fix, then cleaning things up
> ex-post by cherrypicking.  (My apologies to Stefan ... I really
> oughtta have this hooked into diff-mode somehow! :-)
> 
> I find that mode of work painful in Mercurial because of the
> 500-1000ms delay for the commit.  I assume that bzr would be similar
> because of the overhead of starting up the Python interpreter.

You do know hg has a record extension, right? Just throw "hgext.record="
into the extensions section of your ~/.hgrc, then you can use "hg record".
--