RFC: Machine-readable merge requests

James Henstridge james at jamesh.id.au
Thu Feb 15 15:51:13 GMT 2007

On 15/02/07, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> Hash: SHA1
> Hi all,
> I've had some ideas brewing for a while now about providing a standard,
> machine-readable merge request format.  This is what I've come up with:
> http://bazaar-vcs.org/Specs/MergeDirective
> I'd be interested to hear what people think.

I think it needs a few more details about signing.

1. Is it just the RIO blob that gets signed?  From what you've written
it sounds like the diff or bundle don't need to be signed because of
the testament included in the header.
2. How should the merge directive be signed? (clear signed, pgp/mime,
or some other type of dettached signature?)
3. If the merge directive requires that it be signed by multiple keys,
how are those stored?  If you are using clearsigning, each signature
would be signing the previous signature.  Is the order important.


More information about the bazaar mailing list