Patchwork instance "Submitter" attribution and GitGitGadget

>
> Cheers,
> Philippe.
>
> [1] https://patchwork.kernel.org/project/git/list/?submitter=182351

> On Sat, 18 Jan 2020, Philippe Blain wrote:
>
>> I’ve noticed that all (I think) patch series sent to the list using
>> Gitgitgadget are attributed to Dscho (Submitter is "Johannes Schindelin
>> via GitGitGadget") on the patchwork instance [1]. I don’t know if you
>> are aware of that or if there’s a way to fix it in patchwork…
>
> Right now, it shows "Lucius Hu via GitGitGadget". Clearly, patchwork uses
> only the email address as identifier, being unprepared to accept that the
> same email address might be used by multiple contributors.

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Sat, 18 Jan 2020, Philippe Blain wrote:
> >
> >> I’ve noticed that all (I think) patch series sent to the list using
> >> Gitgitgadget are attributed to Dscho (Submitter is "Johannes Schindelin
> >> via GitGitGadget") on the patchwork instance [1]. I don’t know if you
> >> are aware of that or if there’s a way to fix it in patchwork…
> >
> > Right now, it shows "Lucius Hu via GitGitGadget". Clearly, patchwork uses
> > only the email address as identifier, being unprepared to accept that the
> > same email address might be used by multiple contributors.
>
> Would it help to use the "Sender:" header?  IIUC right now GGG
> records its name on "From:" with its e-mail and a human-readable
> name derived from the author of the ptach, but if it can record the
> true author on "From:" and leave GGG's name on the "Sender:", would
> patchwork use the "From:" side of the identity instead?

> If that works, it would have an additional benefit of not having to
> add the in-body "From:" to override the mail-header "From:", to avoid
> attributing the authorship to GGG.
>
>
>

> > Would it help to use the "Sender:" header?  IIUC right now GGG
> > records its name on "From:" with its e-mail and a human-readable
> > name derived from the author of the ptach, but if it can record the
> > true author on "From:" and leave GGG's name on the "Sender:", would
> > patchwork use the "From:" side of the identity instead?
> 
> To tie up that loose end: GMail seemed to insist in my tests on replacing
> the `From:` header, therefore we cannot implement this `Sender:` idea, not
> using GMail to deliver the GitGitGadget patch series at least.

> On Thu, Jan 07, 2021 at 03:35:54PM +0100, Johannes Schindelin wrote:
> > > Would it help to use the "Sender:" header?  IIUC right now GGG
> > > records its name on "From:" with its e-mail and a human-readable
> > > name derived from the author of the ptach, but if it can record the
> > > true author on "From:" and leave GGG's name on the "Sender:", would
> > > patchwork use the "From:" side of the identity instead?
> >
> > To tie up that loose end: GMail seemed to insist in my tests on replacing
> > the `From:` header, therefore we cannot implement this `Sender:` idea, not
> > using GMail to deliver the GitGitGadget patch series at least.
>
> Can you possibly set X-Original-From: in the header?

> Patchwork almost does the right thing with it, though right now it
> expects that the From: will be set to the list's email address (which is
> only correct for google groups).
>
> We have a workaround for the current situation on patchwork.kernel.org [1],
> but it requires parsing the body of the message instead of just relying on the
> headers.
>
> > > If that works, it would have an additional benefit of not having to
> > > add the in-body "From:" to override the mail-header "From:", to avoid
> > > attributing the authorship to GGG.
>
> Using the in-body From: is both good and proper for such service. Trying to
> put the author's email into the actual From will run afoul of SPF.

>
> -K
>
> [1] https://git.kernel.org/pub/scm/infra/patchwork/procmail.git/tree/git.rc
>