bzr-svn, round 2

[John Arbash Meinel]

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


...
>> I've been watching that branch, and would like to try it out.  I'm a
>> bit fearful of the outcome though.  I'd really like for annotate to
>> show the merge revision's information rather than question marks about
>> when a change was made and who made it.  This is kind of the same
>> argument as the log <path> stuff.  I really want to know any
>> information you have rather than skipping over an interesting piece of
>> history because you don't have the full branch of information behind
>> it.
> From all I hear it sounds like what you're really after is indeed the
> push_merged_revisions setting. Pushing without the merged revisions
> implies ghosts and there's no way we can make up information we don't
> have, the information you'd like bzr to display in annotate.

Well, a rebase (dcommit/dpush) style flow would at least annotate it to
the merge revision, which is some of what he mentioned.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwJWscACgkQJdeBCYSNAANuEACeIM20CqdL33Ro6FM/7QRHAoCT
6LcAoJT/24WgdjPJJeI7Ox2KuEio/Foe
=oeH4
-----END PGP SIGNATURE-----