Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAHk-=wjS6cjjP+fkZWzzrdZ_fZ1F=PrAGcBc57vKCpNyoD73Vw@mail.gmail.com>
 <CACRpkdbi2gqqc271eMgHjD68bqf2mzw8zw+iAhYv2LFajfo-eQ@mail.gmail.com>
 <CAHk-=wiiC65aZFrDp69vdcSALLDZNPkTL1diadxNL54tBPeAzQ@mail.gmail.com> <20181023093521.dm3l5oen2j7etsot@kshutemo-mobl1>
In-Reply-To: <20181023093521.dm3l5oen2j7etsot@kshutemo-mobl1>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue, 23 Oct 2018 10:46:06 +0100
Message-ID: <CAHk-=wh6i5t5jYHrC-ZCdj8qoZWP3BptV87U=G9G4UyunzPf7Q@mail.gmail.com>
Subject: Re: Git pull ack emails..
To:     kirill@shutemov.name
Cc:     Linus Walleij <linus.walleij@linaro.org>,
        Boris Brezillon <boris.brezillon@bootlin.com>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Christoph Hellwig <hch@lst.de>,
        Guenter Roeck <linux@roeck-us.net>,
        Jacek Anaszewski <jacek.anaszewski@gmail.com>,
        Jens Axboe <axboe@kernel.dk>, Mark Brown <broonie@kernel.org>,
        Ulf Hansson <ulf.hansson@linaro.org>,
        Greg KH <gregkh@linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Oct 23, 2018 at 10:35 AM Kirill A. Shutemov
<kirill@shutemov.name> wrote:
>
> Can you tag merge commit with message-id of the pull request?
> Automation machinery can reply to the pull request with proper CC list
> obtained from the archive?

If it's a "proper" pull request (ie done by git request-pull), then
the magic marker would be that it as that

    for you to fetch changes up to %H:

line where %H is the hash of the tip of the tree that is requested to be pulled.

Then automation could literally just check "is that commit in Linus'
public tree", and when that happens, generate an automatic
notification that the pull request in question has been merged.

So this could all be automated for people who really want to automate
it. I'm not sure I want to do _that_ kind of automation, though. That
sounds more like "maybe something like that would make sense as an
extension of a patchwork-like tool".

I thik I'll just try the "ack when starting the pull" model and see
how that works. Maybe I was overthinking it.

And if it turns out that it would be better to ack after everything
has passed, I could easily just do an email filter for "messages that
are to me, but I have archived and not replied to, and that have 'git
pull' in them".

I use email filters for pinpointing the pulls to begin with, I could
just use email filters to pinpoint the pull requests that I have
already handled.

                Linus