git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Patchwork now does the right thing with GGG submissions
Date: Mon, 12 Oct 2020 17:27:36 -0400	[thread overview]
Message-ID: <20201012212736.vb7qq3hcdkdnqvnq@chatter.i7.local> (raw)
In-Reply-To: <xmqq362jnpuw.fsf@gitster.c.googlers.com>

On Mon, Oct 12, 2020 at 01:36:39PM -0700, Junio C Hamano wrote:
> >> Just FYI, I made the necessary tweaks to patchwork to make it 
> >> properly
> >> assign "From" for gitgitgadget submissions:
> >>
> >> https://patchwork.kernel.org/patch/11832689/
> >
> > \o/ Thanks much for this.
> >
> > For the curious, any links to the change behind the scenes that made
> > that happens?  Does it use Sender[1] or a different field?  Does the
> > change live in [2] or [3]?
> >
> > Sincerely,
> > Jonathan
> 
> It is curious that I sometimes see you respond to Konstantin on this
> list, but the message you are responding to is not found.  What is
> going on?

I initially didn't send it to git@vger, only to Jonathan. :) I don't 
mind, though -- I just wasn't sure if this was something others on the 
git list would care about.

> A question to Konstantin is what is so special about GGG?  Did you
> make patchwork to pay attention to the in-body "From:" and other
> in-body header lines (in which case it benefits not just GGG but
> everybody).  If you added a support to ignore everything before the
> scissors that would deserve an extra gold star ;-)

No, this is specifically for GGG mail, as it's a very specific 
well-understood case. The solution I have in place is to just pay 
attention to the in-body Form, but once we upgrade to patchwork 2.2.2 
tomorrow, we will also start paying attention to the X-Original-From 
header.

I'm not 100% sure if it's always correct to pay attention to the in-body 
From -- at least for the purposes of patchwork. Patchwork pays attention 
to "who submitted the series," not "who authored the commit," so making 
in-body From always be the "From" in patchwork would be wrong.

For the cases of GGG, we can ignore this difference, as we definitely 
don't want to pay attention to "who sent the patch" (it's always 
gitgitgadget@gmail.com). However, GGG can make the situation more 
correct if it starts adding an X-Original-From that would be the Github 
name and email of the person submitting the pull request. E.g.:

From: D. Eveloper via GitGitGadget <ggg@gmail.com>   <- DMARC From
X-Original-From: D. Eveloper <github@email.here.com> <- Patchwork From
Subject: [PATCH 1/10] ...

From: A. Nother-Person <foo@example.com>             <- Git From

> For example, how does
> 
> https://lore.kernel.org/git/xmqqy2kwiimi.fsf@gitster.c.googlers.com/
> 
> appear in patchwork?

It's a reply to another patch, so patchwork only processes it as a 
comment. Generally, patchwork doesn't see worrying about this thing as 
its job -- it just wants to let maintainers track incoming patches and 
series and download them in a format that is easy to apply using "git 
am". For that matter, that's how b4 approaches this as well.

-K

  reply	other threads:[~2020-10-12 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201012180034.tu4rmeoadhy5j4w7@chatter.i7.local>
2020-10-12 19:38 ` Patchwork now does the right thing with GGG submissions Jonathan Nieder
2020-10-12 20:36   ` Junio C Hamano
2020-10-12 21:27     ` Konstantin Ryabitsev [this message]
2020-10-12 21:31   ` Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201012212736.vb7qq3hcdkdnqvnq@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).