Re: [Ksummit-discuss] Allowing something Change-Id (or something like it) in kernel commits

Doug Anderson
2019-09-16T18:05:48Z

Hi,

On Mon, Sep 16, 2019 at 10:43 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> On Mon, Aug 26, 2019 at 04:11:12PM -0700, Doug Anderson wrote:
>
> > Sigh. Email is so hard to communicate over. I'm not intending to
> > include the Message-Id in the commit. I'm intending to use the
> > Change-Id _in_ the Message-Id. The Message-Id already has a bunch of
> > random characters in it. Why not make them useful for something?
>
> *blink*
>
> I must be misreading you; are you *really* suggesting to update
> every MUA people are using? Or researching and documenting
> the ways to control said MUAs to achieve the effect.
>
> I don't know how to get that in mutt(1), TBH. And then there are
> poor sods who use browsers/evolution/pine/whatnot for that...

In general I think most people send patches with git-send-email. If
you use git-send-email you can simply add a Message-Id into your patch
files before passing them to git-send-email and it'll use that. If
you use mutt to directly send a patch then, right, it won't get a
message ID like this. I think expecting 100% adoption is impossible,
so for now I'm hoping to get sufficient adoption that it could be
worth it for someone to do the tools integration.

FYI: I personally use patman to send my patches (which eventually
passes them to git-send-email). The patman change to setup the
Message-Id is at:

https://patchwork.ozlabs.org/patch/1157266/

Johannes Berg also responded to my patch providing a proof of concept
way to use a git hook.

NOTE: for responses to patches (where it's more likely people will use
mutt) there is no need for magic Message-Id. There are already plenty
of ways to track responses to emails.

-Doug
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org