archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Bjorn Helgaas <>
	Linux Kernel Mailing List <>,
	Lorenzo Pieralisi <>
Subject: Re: [GIT PULL] PCI changes for v5.6
Date: Fri, 31 Jan 2020 14:49:52 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jan 31, 2020 at 2:34 PM Bjorn Helgaas <> wrote:
>   git:// 01b810ed7187

You must have screwed up your git request-pull somehow.

Yes, yes, the above works, and a branch is just a named SHA1. You can
give the SHA1 directly.

But it's not what you meant to do, I'm sure. Especially since you
pointed to the SHA1 of the top commit, not the tag that you have that
points to it.

I can see what you _meant_ to ask me to pull with "git ls-remote". I
clearly should - and will - pull the 'pci-v5.6-changes' tag, which
points to that commit.

But can you check what in your workflow went wrong for the above to happen?


  reply	other threads:[~2020-01-31 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 22:34 Bjorn Helgaas
2020-01-31 22:49 ` Linus Torvalds [this message]
2020-02-01 18:37   ` Bjorn Helgaas
2020-01-31 23:10 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \
    --subject='Re: [GIT PULL] PCI changes for v5.6' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).