From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] hwmon updates for hwmon-for-v5.3
Date: Thu, 11 Jul 2019 15:26:51 -0700 [thread overview]
Message-ID: <CAHk-=wh4B5D2nd66iqCTzbY9bhtDn3WxpZCNc4hM9zOL+iJGBQ@mail.gmail.com> (raw)
In-Reply-To: <20190711221948.GA16140@roeck-us.net>
On Thu, Jul 11, 2019 at 3:19 PM Guenter Roeck <linux@roeck-us.net> wrote:
>
> I have been sending out those odd messages ever since v5.1 because
> my script was checking for v4.x, not for v5.x. Oh well.
> Should I resend with better subject and text ?
I nbever even noticed any oddity.
As long as I see "git" and "pull" in an email that is directed to me,
it gets caught in my filter for pull requests. The rest is gravy,
although I'll complain if it doesn't have the expected diffstat and
explanation for my merge commit message.
The "for hwmon-for-v5.3" instead of just "for 5.3" difference I didn't
even notice before you just pointed it out.
And I've actually already merged your pull request., it just hasn't
been pushed out yet. It was just delayed by (a) my normal "merge
similar subjects together as batches" and then by (b) the 24-hour
merge hiatus as I was fighting my machines not booting due to a couple
of independent bugs this merge window that just happened to hit me.
Linus
next prev parent reply other threads:[~2019-07-11 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 18:23 [GIT PULL] hwmon updates for hwmon-for-v5.3 Guenter Roeck
2019-07-11 22:19 ` Guenter Roeck
2019-07-11 22:26 ` Linus Torvalds [this message]
2019-07-11 22:30 ` pr-tracker-bot
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='CAHk-=wh4B5D2nd66iqCTzbY9bhtDn3WxpZCNc4hM9zOL+iJGBQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).