Blog post on git vs. bzr movement history

[Aaron Bentley]

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

James Westby wrote:
> Hi,

> I tend to agree with him, and I was going to write something similar,
> but he beat me to it.

I'm not sure I agree with his thesis.  I'd rate them as about equally
important.  I'm certainly starting to get annoyed by this "Bazaar is
only for distributions" meme that people are spreading around.

Git's decision to forgo file tracking is an architectural decision.
Bazaar's lack of function tracking is an implementation issue.  We could
do it like git.  Or we could aim higher.  git's annotation across code
moves doesn't work if you also rename files:

http://kerneltrap.org/node/11765

> The after the fact processing to detect moves and copies seems to
> support this much better, and upfront specification would become unruly
> for some changes I would guess.

It's possible, and I think cheapest, to detect text block movement at
commit time.  The upfront specification is not strictly necessary, just
as we don't make you confirm annotations.  That enables data/storage
models where merging and annotating across block movements is so cheap
that you make it the default.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGpn2A0F+nu1YWqI0RAihWAJ4mA1+3W9jLPwc/ZiUTrarqXl+YnACeIrwd
TA+dM4f2FezDrotViWA2kwY=
=dk6q
-----END PGP SIGNATURE-----