Patchwork lists submitters @google.com as "Rick Altherr via openbmc"

Patchwork lists submitters @google.com as "Rick Altherr via openbmc"

[Xo Wang]

Hey folks,

I think Patchwork has decided that the email openbmc@lists.ozlabs.org
now maps to the author of the first patch originating from that email
(Rick Altherr @ Google).

So all of the patches from @google.com proxied by Mailman are now
showing up as authored by Rick:
https://patchwork.ozlabs.org/project/openbmc/list/?submitter=70875&archive=both&state=*

Since Joel is presumably picking from Patchwork to GitHub, the git
author info might be a bit unreliable. You'll have to peek at the
Signed-off-by: for the Google blames. :)

cheers
xo

Re: Patchwork lists submitters @google.com as "Rick Altherr via openbmc"

[Joel Stanley]

On Wed, Feb 8, 2017 at 8:46 AM, Xo Wang via openbmc
<openbmc@lists.ozlabs.org> wrote:
> Hey folks,
>
> I think Patchwork has decided that the email openbmc@lists.ozlabs.org
> now maps to the author of the first patch originating from that email
> (Rick Altherr @ Google).
>
> So all of the patches from @google.com proxied by Mailman are now
> showing up as authored by Rick:
> https://patchwork.ozlabs.org/project/openbmc/list/?submitter=70875&archive=both&state=*
>
> Since Joel is presumably picking from Patchwork to GitHub, the git
> author info might be a bit unreliable. You'll have to peek at the
> Signed-off-by: for the Google blames. :)

Submitter 70875 is now known as "Unknown sender due to SPF". This
looks ugly, but does save me from applying misattributed patches.

I have made some tweaks to the mailing list settings that might let
DMARC'd mail get through. I have turned off the munging and will keep
an eye out for missed mail. If it's still broken I will have to turn
it back on.

Xo (or any other @google.com account holder), if you could reply to
this thread without ccing me that would be a good test.

Cheers,

Joel

Re: Patchwork lists submitters @google.com as "Rick Altherr via openbmc"

[Rick Altherr]

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

Testing... Testing... Is this thing on?

On Feb 8, 2017 7:05 PM, "Joel Stanley" <joel@jms.id.au> wrote:

> On Wed, Feb 8, 2017 at 8:46 AM, Xo Wang via openbmc
> <openbmc@lists.ozlabs.org> wrote:
> > Hey folks,
> >
> > I think Patchwork has decided that the email openbmc@lists.ozlabs.org
> > now maps to the author of the first patch originating from that email
> > (Rick Altherr @ Google).
> >
> > So all of the patches from @google.com proxied by Mailman are now
> > showing up as authored by Rick:
> > https://patchwork.ozlabs.org/project/openbmc/list/?
> submitter=70875&archive=both&state=*
> >
> > Since Joel is presumably picking from Patchwork to GitHub, the git
> > author info might be a bit unreliable. You'll have to peek at the
> > Signed-off-by: for the Google blames. :)
>
> Submitter 70875 is now known as "Unknown sender due to SPF". This
> looks ugly, but does save me from applying misattributed patches.
>
> I have made some tweaks to the mailing list settings that might let
> DMARC'd mail get through. I have turned off the munging and will keep
> an eye out for missed mail. If it's still broken I will have to turn
> it back on.
>
> Xo (or any other @google.com account holder), if you could reply to
> this thread without ccing me that would be a good test.
>
> Cheers,
>
> Joel
>

[-- Attachment #2: Type: text/html, Size: 2127 bytes --]

Re: Patchwork lists submitters @google.com as "Rick Altherr via openbmc"

[Joel Stanley]

On Thu, Feb 9, 2017 at 2:43 PM, Rick Altherr <raltherr@google.com> wrote:
> Testing... Testing... Is this thing on?

Woot! It works.

I'll leave DMARC rewriting off. Keep an eye out for regressions - if
you think I've started ignoring your emails please ping me on IRC.

Cheers,

Joel