From: Linus Torvalds <torvalds@linux-foundation.org>
To: Eduardo Valentin <edubezval@gmail.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: pr-tracker-bot@kernel.org, Rui Zhang <rui.zhang@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Thermal-SoC management fixes for v5.0-rc6
Date: Mon, 11 Feb 2019 10:34:09 -0800 [thread overview]
Message-ID: <CAHk-=wgz_WpD7jc084QROuM0zszEG0-WvQhQZPsCboMOWNRiWw@mail.gmail.com> (raw)
In-Reply-To: <20190211031921.GA1799@localhost.localdomain>
On Sun, Feb 10, 2019 at 7:19 PM Eduardo Valentin <edubezval@gmail.com> wrote:
>
> On Sun, Feb 10, 2019 at 04:25:16AM +0000, pr-tracker-bot@kernel.org wrote:
> > The pull request you sent on Sat, 9 Feb 2019 20:17:23 -0800:
> >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes
> >
> > has been merged into torvalds/linux.git:
> > https://git.kernel.org/torvalds/c/7ad915f5ebf5b9e7ca98a7048d8f84a631fe388b
>
> I think the bot is off here because the above commit is about a merge
> from the linux-omap tree from Tony.
Indeed.
.. and the pr-tracker-bot thing actually made me ignore the pull
request, thinking I had left it in my inbox despite having pulled it.
So it would be really good to know why pr-tracker-bot ended up
replying to the wrong email, because it can cause real problems.
Linus
next prev parent reply other threads:[~2019-02-11 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 4:17 [GIT PULL] Thermal-SoC management fixes for v5.0-rc6 Eduardo Valentin
2019-02-10 4:25 ` pr-tracker-bot
2019-02-11 3:19 ` Eduardo Valentin
2019-02-11 18:34 ` Linus Torvalds [this message]
2019-02-11 18:40 ` Konstantin Ryabitsev
2019-02-11 20:05 ` Konstantin Ryabitsev
2019-02-11 20:16 ` Konstantin Ryabitsev
2019-02-11 22:04 ` Linus Torvalds
2019-02-11 23:10 ` Konstantin Ryabitsev
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-=wgz_WpD7jc084QROuM0zszEG0-WvQhQZPsCboMOWNRiWw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=edubezval@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pr-tracker-bot@kernel.org \
--cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).