[BUG] apply_changeset / generate_changeset use wrong base

[Aaron Bentley]

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

Aaron Bentley wrote:
> I would actually prefer if by default, it always picked the last commit
> in OTHER_BRANCH as the changeset base, because that makes it clearer
> what will happen to the target tree if the changeset is applied.

I take it back.  Using the common ancestor as the changeset base will
show the differences most clearly.

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

iD8DBQFDOY2c0F+nu1YWqI0RAiJ8AJ9F8sok4zUDRh3iJ9Jb8ycdpJJUbACeOzY8
S9DKDaXCvoUhJwsqbW88xko=
=Gywj
-----END PGP SIGNATURE-----