LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <email@example.com>
To: Linus Walleij <firstname.lastname@example.org>
Cc: Boris Brezillon <email@example.com>,
Catalin Marinas <firstname.lastname@example.org>,
Christoph Hellwig <email@example.com>,
Guenter Roeck <firstname.lastname@example.org>,
Jacek Anaszewski <email@example.com>,
Jens Axboe <firstname.lastname@example.org>, Mark Brown <email@example.com>,
Ulf Hansson <firstname.lastname@example.org>,
Greg KH <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>
Subject: Re: Git pull ack emails..
Date: Tue, 23 Oct 2018 10:10:47 +0100 [thread overview]
Message-ID: <CAHk-=wiiC65aZFrDp69vdcSALLDZNPkTL1diadxNL54tBPeAzQ@mail.gmail.com> (raw)
On Tue, Oct 23, 2018 at 9:53 AM Linus Walleij <email@example.com> wrote:
> Can't you just tool something that mails automatically after-the-fact?
So a certain amount of simple/stupid automation would be possible.
That's how the participants list in this email was generated, but the
script I used was actually a pretty much garbage one-liner that just
happens to work for most cases.
It just did my usual "mergelog" (which is a bit like "git shortlog",
it's a script to just get the summary of my merges instead of the
general git logs) and then it used the result of that lookup to look
up the email address by just matching committers.
But it's broken to the point of almost being useless for a couple of reasons:
- my mergelog names don't necessarily match any name in the git history.
For example, Greg goes by "Greg KH" when I merge from him, because
I'm lazy and feel like I don't want to mis-type his name, which I've
done too many times. But in the actual git history, he goes by the
full "Greg Kroah-Hartman", so my stupid script would have messed him
At the other end of the spectrum, people with complex characters
have their names copied-and-pasted from their email or the signature
from their tag, and sometimes those then don't match either.
- some people use one email for "official" purposes (ie company email
etc) in the git history, but actually tend to *use* another email
(because sometimes the company email is slow and/or broken).
- it wouldn't get the usual mailing list cc's etc, and those might be
the most important ones. It is how I saw Greg's replies, after all.
So I feel that he automation model is just not good. The reply should
go to the actual pull request, not to the git history. People who want
just _that_ could already automate the git history thing without me
even doing anything at all, either scripting it themselves or by using
some filtering on the kernel commit mailing list..
So I happened to use the automation model for this email thread, but I
think it's actually the worst of all worlds.
next prev parent reply other threads:[~2018-10-23 9:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 8:41 Linus Torvalds
2018-10-23 8:53 ` Linus Walleij
2018-10-23 9:10 ` Linus Torvalds [this message]
2018-10-23 9:35 ` Kirill A. Shutemov
2018-10-23 9:45 ` Mark Brown
2018-10-23 9:46 ` Linus Torvalds
2018-10-23 20:04 ` Konstantin Ryabitsev
2018-10-25 14:13 ` Linus Torvalds
2018-10-26 17:36 ` Rob Herring
2018-10-26 21:15 ` Mark Brown
2018-11-01 10:18 ` Michael Ellerman
2018-11-07 10:41 ` Boris Brezillon
2018-11-07 23:56 ` Michael Ellerman
2018-10-31 14:27 ` Konstantin Ryabitsev
2018-10-31 18:34 ` Linus Torvalds
2018-10-23 9:02 ` Willy Tarreau
2018-10-23 9:15 ` Linus Torvalds
2018-10-23 9:23 ` Takashi Iwai
2018-10-23 9:15 ` Ingo Molnar
2018-10-23 9:17 ` Boris Brezillon
2018-10-23 9:47 ` Mark Brown
2018-10-23 9:19 ` Mark Brown
2018-10-23 9:25 ` Greg KH
2018-10-23 9:51 ` James Morris
2018-10-23 9:56 ` Jens Axboe
2018-10-23 12:13 ` Ulf Hansson
2018-10-23 20:41 ` Jacek Anaszewski
2018-10-23 20:01 ` Olof Johansson
2018-10-24 22:21 ` Kees Cook
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: Git pull ack emails..' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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 NNTP newsgroup(s).