brisbane: initial cut at a mergeline cache
Aaron Bentley
aaron at aaronbentley.com
Wed Apr 1 15:30:11 BST 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthew D. Fuller wrote:
> I've preferred merge-point-based numbering since we had the
> dicussion when dotted revnos were being implemented.
+1.
> It also has other advantages; picture reading through a long --long
> (well, with -n0 now) on something like bzr.dev, where each mainline
> rev is a merge of dozens or hundreds of revs. With merge-point-based
> numbering, you know about where you are in the history. With
> ancestral, you don't, and if you're flipping through it fast you can
> even blow right past the next (previous) mainline rev without even
> noticing it.
My primary use case for log --long -n1 is finding which revision merged
another revision, so merge-point numbering would help me avoid that
entirely.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknTenMACgkQ0F+nu1YWqI3QQACgh+IHPWoFYl7rdhaqcDllWWQF
Hm4An3pY0IEd7dY6dZW5Ouc4+O6rwRwk
=Nd8l
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list