From: Benson Leung <bleung@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
dtor@chromium.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Olof Johansson <olof@lixom.net>,
Guenter Roeck <linux@roeck-us.net>,
enric.balletbo@collabora.com,
Gwendal Grignou <gwendal@chromium.org>
Subject: Re: [GIT PULL] chrome-platform updates for v4.17
Date: Fri, 13 Apr 2018 16:32:44 -0700 [thread overview]
Message-ID: <20180413233244.GA108443@decatoncale.mtv.corp.google.com> (raw)
In-Reply-To: <CA+55aFwSStqgd-i86ubpLRWPiYTyC=Km--t2C0TF1UqMUv0kgg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Fri, Apr 13, 2018 at 04:26:41PM -0700, Linus Torvalds wrote:
> Please don't do this to me.
>
> You're sending me a pull request in the second half of the second week
> of the merge window, and none of this has been in linux-next as far as
> I can tell.
>
> I don't even check linux-next as of when the merge window opened - I
> check it as of "one week into the merge window".
>
> Ok, ok, I do in fact find two of the commits in linux-next, but even
> they have been rebased for some reason.
>
> The others? I can't find them even in some rebased form.
>
> I'll take this for now, but next time I see this kind of "late in the
> merge window, absolutely zero exposure anywhere else", I'll just skip
> the whole pull request. Don't do it.
Sorry about that, Linus. Won't happen again.
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-04-13 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 22:21 Benson Leung
2018-04-13 23:26 ` Linus Torvalds
2018-04-13 23:32 ` Benson Leung [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=20180413233244.GA108443@decatoncale.mtv.corp.google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=olof@lixom.net \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome