[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Changeset submissions for merge requests

From: Yann Droneaud
Subject: Re: [Gnu-arch-users] Changeset submissions for merge requests
Date: Fri, 03 Sep 2004 21:27:25 +0200
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)

Andrew Suffield <address@hidden> writes:

> Support for formally capturing changeset submissions is now active. A
> merge request is mapped by number to a branch, like this:
> address@hidden/tla-merges--merge-49--0
> Merge requests can and should contain the following pseudo-header
> fields, which are used to construct the branch:
> Archive-URI
>         This gives the URI at which your archive can be found. It's
>         only strictly necessary the first time you submit something
>         from the given archive, after which it stays registered on the
>         server. If you need to *change* the registered URI, you have
>         to talk to me.
> Base-Revision
>         This gives the revision which your changes should be applied
>         against. Anything accepted by tag will work; you can say
>         'address@hidden/tla--devo' to grab whatever is the latest
>         at that time. Make sure that your changes actually apply
>         against the named revision, or they will be rejected.
> Revision
>         This is a comma-delimited list of revisions to be
>         applied (or you can use multiple Revision fields, or mix the
>         two; they'll be folded into a single list). It'll be fed to
>         replay --list, so you have to list precisely the changesets to
>         be applied - no ranges or following ancestry.

Could you update with those informations.

And, especially update, adding the example,
or i will make many errors as the stupid user i am (and i don't want to
pollute more the bug tracking system)


Yann Droneaud (aka Meuh) <address@hidden> |
Une vache perdue sur Internet | A cow lost in the Internet
1024D/BEA43321   5D91 B5B0 5137 B8FE 6882  FE19 CAA0 6F05 BEA4 3321

reply via email to

[Prev in Thread] Current Thread [Next in Thread]