LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: linux-rtc@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] RTC for 4.15
Date: Wed, 22 Nov 2017 21:05:27 -1000	[thread overview]
Message-ID: <CA+55aFznZnY_1-puQms6jm9nonAooDvTbvUqZjZ8bC0PGboLmg@mail.gmail.com> (raw)
In-Reply-To: <20171121152823.payahwcvnnjervgf@piout.net>

On Tue, Nov 21, 2017 at 5:28 AM, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
>
> The last minute change is only a documentation update to avoid further
> bug reports. (And also a small commit message reword).

This is _really_ annoying.

I'm checking that pull requests have been in linux-next, and that
rewording of the commit message just means that now that  commit
doesn't trigger as being in commit-next and I have to go chase it down
or just say "screw this, it adds a whole new driver that wasn't in
linux-next".

Guess which one is easier for me to do?

So don't do this crap.

I ended up looking up the original commit, but dammit, I'm not happy
about this. Why wasn't the RTC stuff sent last week like I asked
people to do? Now I'm in the middle of travels, and having to figure
out what parts were in linux-next to verify that it actually has
gotten at least some real test coverage, and that I'm not pulling
random stuff.

                Linus

      reply	other threads:[~2017-11-23  7:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 15:28 [GIT PULL] RTC for 4.15 Alexandre Belloni
2017-11-23  7:05 ` Linus Torvalds [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=CA+55aFznZnY_1-puQms6jm9nonAooDvTbvUqZjZ8bC0PGboLmg@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).