Patch tagging/classification

Yann E. MORIN yann.morin.1998 at
Tue Feb 9 08:00:49 AEDT 2016

Damien, All,

On 2016-02-08 15:02 +0000, Damien Lespiau spake thusly:
> I think I'd like to see a tool to wrap git
> send-email, that would ensure a more deterministic way of sending
> patches and updates after review see:

Not sure that would fit your needs (at least not as described in the PR
you linked above), but I have a git wrapper around send-email +

It's basically:

    git format-patch BASE..HEAD
    git request-pull BASE..HEAD >msg
    # some tweaking of msg
    ${EDITOR} msg
    git send-email msg *.patch

with a little bit of sugar: options to control who is in to, cc, bcc,
whether cover-letter is to-ed, cc-ed or bcc-ed to patch authors, whether
to hint patchwork to ignore cover-letter and/or patches, set the version
of the series, add a '[tag]' suffix (e.g. RFC) and so on...

Mails would be sent as (N patches, version M, RFC suffix):

    [PATCH 0/N vM RFC] bla bla bla (branch BRANCH-NAME)
    +- [PATCH 1/N vM RFC] bla bla foo
    +- [PATCH 2/N vM RFC] bla bla bar

>From your exposed needs, I can see '--in-reply-to' to be missing, but
that can probably be added quite easily. I'm not sure what you call a
'series id', though, but if you refer to a branch name, it's already

Comments most welcome, of course. ;-)

BTW, there's also git-pwc in that repository, a simple dialog-based
pwclient-based frontend to select and apply patches:

(Warning: written for my personal use, might be rough on the edges, won't
be big and professional like... you know the tune! ;-) ).

Yann E. MORIN.

|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |

More information about the Patchwork mailing list