[RFC] merge - common_ancestor generation
Aaron Bentley
aaron.bentley at utoronto.ca
Tue Mar 7 04:42:13 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
| On Mon, 2006-03-06 at 21:15 -0500, Aaron Bentley wrote:
|>The graph root should always be the NULL_REVISION, except in cases where
|>the NULL_REVISION is unreachable due to ghosts, in which case we can fail.
|
|
| I think we should not fail in that case, rather report all the ghosts as
| roots (they are) and let the caller decide what they want to do -
| whether to synthesis a common ancestor, or to work off the known graph.
Okay, I agree that this is better as we move forward.
| Can you confirm this matches what we spoke about?
Yes, this looks right.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEDQ8l0F+nu1YWqI0RAleBAJ9gjz7jCjAZ3VHx/BOtUNvNKaSrRgCaAuCx
L10D3jkGbc712nTpGvwJmb0=
=1dJO
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list