[BUG] apply_changeset / generate_changeset use wrong base

[Aaron Bentley]

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

John A Meinel wrote:
> Yes, this I know of this limitation in the current implementation. There
> is even a comment in "apply_changeset" which states this.

Okay.  I had seen that, but clearly got the wrong idea from our last
conversation about this, because I wasn't sure how you wanted to fix it.

> I think the trick would just be to call:
> 
> base = common_ancestor(cset_info.target, branch.last_patch())

Okay, I can do that.

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

iD8DBQFDOVzY0F+nu1YWqI0RAvuJAJwKWhodYFVs388F5D6mE5DXmkE1YgCZAdZO
nRvkfbAuy2VKvQGrDMMb8Xs=
=zh5N
-----END PGP SIGNATURE-----