From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <bp@suse.de>
Cc: Ard Biesheuvel <ardb@kernel.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] efi/urgent for v5.9-rc6
Date: Sun, 20 Sep 2020 15:25:12 -0700 [thread overview]
Message-ID: <CAHk-=witaxLCP4ZoxywTkJrcd3n+yBBJ46j3obsSFrcWK2Yjpg@mail.gmail.com> (raw)
In-Reply-To: <20200920193312.GD13044@zn.tnic>
On Sun, Sep 20, 2020 at 12:33 PM Borislav Petkov <bp@suse.de> wrote:
>
> I'm simply forwarding Ard's tag, I hope that's ok.
That's ok, although it shows perhaps a weakness in our model.
Git actually would have allowed you to create a signed tag pointing to
Ard's tag, and we'd have had the signature chain that way. Although
I'm not even sure the commit signature code has then ever been tested
with that kind of odd situation.
But that might have technically been the best way of doing things
(kind of like sign-offs on commits when forwarding them in email), but
I don't think it really matters.
I just mentioned this odd tag forwarding in the merge commit instead.
It all looks fine, it's just a bit unusual.
Linus
next prev parent reply other threads:[~2020-09-20 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 19:33 [GIT PULL] efi/urgent for v5.9-rc6 Borislav Petkov
2020-09-20 22:25 ` Linus Torvalds [this message]
2020-09-20 22:38 ` Borislav Petkov
2020-09-20 22: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='CAHk-=witaxLCP4ZoxywTkJrcd3n+yBBJ46j3obsSFrcWK2Yjpg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).