public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [GIT PULL] x86/core for 5.18
Date: Sun, 27 Mar 2022 10:22:17 +0200	[thread overview]
Message-ID: <20220327082217.GU8939@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHk-=whhG15HiqR+WM5M2mMy9F17yVdT8_M0ra0tGJS+5ibrdw@mail.gmail.com>

On Sat, Mar 26, 2022 at 02:53:07PM -0700, Linus Torvalds wrote:
> On Sat, Mar 26, 2022 at 8:26 AM Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > Hi Linus, my first pull request in like forever, so please bear with me.
> >
> > Boris talked me through it, so hopefully it isn't entirely insane :-)
> 
> Well, it's not exactly working too well:
> 
>   fatal: couldn't find remote ref x86_core_for_5.18_rc1
> 
> there is actually a branch called "x86/core" there that has the commit
> you mention as the top commit, but I'm _hoping_ you had a signed that
> you created, and just never pushed out.
> 
> So I won't pull that branch I found, in the hope that there's a simple
> "Oh, let me push that tag out" solution that gets me the signature
> too.

Duh! I pushed the tag to the wrong repo (peterz/queue.git)... I just
pushed it out to tip/tip/git as well, so hopefully it should all work
now.

Thanks!



  reply	other threads:[~2022-03-27  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 15:26 [GIT PULL] x86/core for 5.18 Peter Zijlstra
2022-03-26 21:53 ` Linus Torvalds
2022-03-27  8:22   ` Peter Zijlstra [this message]
2022-03-27 17:47     ` Linus Torvalds
2022-03-27 18:55       ` Ingo Molnar
2022-03-27 17:36 ` 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=20220327082217.GU8939@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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