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

[Aaron Bentley]

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

Martin Pool wrote:
> On 29 Jun 2005, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> 
>>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?
> 
> 
> In the current code you'd need the text-id to generate the right
> inventory, but they don't really add any value and are a bit of an
> accident of the current implementation.  From talking to Robert is seems
> like a more useful thing to put in there is the revision-id where the
> text was introduced (i.e. the last one where it was changed.)

I assume the actual store ids would be file-id/revision-id pairs.

This makes store ids computable in most cases, but when an ID is
introduced due to a merge, it will not be computable, I think.  So
changesets should be able to specify the revision-id when it is not the
target revision for the changeset.

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

iD8DBQFCwqoa0F+nu1YWqI0RAh2qAJsECYO0UTn1Fj4efIg8jZVyQUdgsgCdGZcm
oGTBfBZaE2RYETAHsZj2qWU=
=I9AM
-----END PGP SIGNATURE-----