From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] first round of SCSI updates for the 5.6+ merge window
Date: Fri, 05 Jun 2020 14:18:11 -0700 [thread overview]
Message-ID: <1591391891.4728.96.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=wjiQmscZHzOYKmMpFoy4h4xF1Mvf9O8i6qtTtS38t6Wsg@mail.gmail.com>
On Fri, 2020-06-05 at 14:11 -0700, Linus Torvalds wrote:
> On Thu, Jun 4, 2020 at 9:55 PM James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-
> > misc
>
> "Already up to date."
>
> Did you forget to force a push? That scsi-misc tag is your tag from
> April 10.
Um, no, shuffles feet ... I actually tagged the wrong branch:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/tag/?h=scsi-fixes
I've tagged the right branch now if you repull the scsi-misc tag.
Sorry about that; I think it's finger memory from so many fixes
updates.
James
next prev parent reply other threads:[~2020-06-05 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 4:55 [GIT PULL] first round of SCSI updates for the 5.6+ merge window James Bottomley
2020-06-05 21:11 ` Linus Torvalds
2020-06-05 21:18 ` James Bottomley [this message]
2020-06-05 21:25 ` Linus Torvalds
2020-06-05 21:41 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 16:06 James Bottomley
2020-04-03 0:40 ` 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=1591391891.4728.96.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).