pull-sigs for bzr.dev

[Robert Collins]

On Tue, 2006-02-21 at 12:45 -0500, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> John A Meinel wrote:
> > I was thinking, though. It seems the pqm interface should probably be
> > expanded anyway. Because right now you just make a request to merge a
> > branch, but you don't give a specific revision, or a checksum, or
> > anything which has the pqm make sure that it is merging what you asked
> > it to merge.
> 
> Yes, I was thinking we should include a revision testament in the request.

we need revid for locating the revision, testament for verification -
note that the testament is useless if the request isn't signed.
(pqm-the-software allows unsigned requests; pqm-the-bzr-instance does
not).

the revid could be passed by adding it to the url like we discusssed way
back:

merge BRANCH;revid=mbp at 0349-85i04395i43 http://bazaar-ng.org/bzr/bzr.dev

However the testament has the revid in it.. I am wondering about two
variations here:

merge
BRANCHURL;revid=mbp at 0349-85i04395i43;testamentsha=aabcdef123412543847198432423/ http://bazaar-ng.org/bzr/bzr.dev

The idea being that the sha of the testament should match.

This gets it all on one line, which the current line orientated pqm
parser appreciates.

Alternatively:

extended-merge
#rio format data here
from: xxx
into: xxx
testament: however-rio-represents-multiline-literals
end-extended-merge



Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060222/29bdf7a1/attachment.pgp