[PLUGIN] bzr changeset now support rollup changesets (and bzr send-changeset)

[Aaron Bentley]

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

Martin Pool wrote:
> * The base is redundant with the first parent and can be removed. 

This introduces the constraint that the changeset can never be relative
to anything except the first parent.  For this branch
A -> B -> C -> D

If I have only A and you want to send D, you could transmit an A -> D
changeset.  If we remove the base-id, you must send A->B, B->C and C->D.

I don't understand what makes the first parent special, compared to the
the second parent.  Or is it just a matter of picking an arbitrary revision?

We could make base-id optional, and send it only when it differs from
the parent-id, but that would mean having a rarely-used codepath for the
case where base-id is set.

Not that I'm set against it, I just thought it relevent to mention that
we're removing (possibly unwanted) capabilities.

> * File ids and parent ids shouldn't normally need to be transmitted: we
>   know precisely which revision this should be applied to, therefore
>   precisely which filename has what id.  File-ids only need to be
>   given in the changeset for newly added files or directories.


Yes, I think you're right about file-ids.  What about text-ids?  I've
never been clear on their status.  Are they intended to be local-only
data?  If not, then since they're part of the inventory SHA-1, they must
be transmitted unless they can be computed, right?

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

iD8DBQFCwqGa0F+nu1YWqI0RAi2/AJ9a//NeBz8TdfIq6xRrrxS8KsAzSgCfTAG3
rikcBPuHZbG7Lm0ey+gyF4E=
=Y2UQ
-----END PGP SIGNATURE-----