From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Travis <travis@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/platform changes for v4.11
Date: Tue, 21 Feb 2017 08:58:38 +0100 [thread overview]
Message-ID: <20170221075838.GA3125@gmail.com> (raw)
In-Reply-To: <CA+55aFwRL_ZydndoYaqFZBnRRnt21=+kmP7tBiryfqvfis6hCg@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Feb 20, 2017 at 5:17 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Mike Travis (2):
> > [...]
> >
> > travis@sgi.com (8):
> > [...]
>
> Btw, can you be a bit more careful when applying patches to make sure
> that the name and email address is actually good?
Yes, will be more careful, sorry about that!
> This seems to be due to some screw-up on Mike's part, since the
> original email seems to have this crap in the headers:
>
> From: "'Mike Travis" <travis@sgi.com>, '@sgi.com
Yeah, that's god-awful ugly - I should have caught it at the latest when looking
over the shortlog so there's really no excuse for missing it ...
> which should never have worked but Mike apparently screwed up some
> script, and mail transport generally has a "let any crap through"
> tendency, but I would have hoped that people who commit these things
> actually react to how bad the end result is.
>
> Mike, please fix whatever braindamage your mail sending model has.
>
> But Ingo and Thomas (I see both of you committing those broken
> patches), please also look at what downstream sends you, and catch it
> early rather than have crap authorship information.
Yeah.
Thanks,
Ingo
prev parent reply other threads:[~2017-02-21 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 13:17 [GIT PULL] x86/platform changes for v4.11 Ingo Molnar
2017-02-21 0:20 ` Linus Torvalds
2017-02-21 7:58 ` Ingo Molnar [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170221075838.GA3125@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox