From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/vmware changes for v5.7
Date: Tue, 31 Mar 2020 12:11:29 -0700 [thread overview]
Message-ID: <CAHk-=wim0vZMxgxmu=eW4pCqExbcJqswEvK=VYuyqkB-40koTg@mail.gmail.com> (raw)
In-Reply-To: <20200331100353.GA37509@gmail.com>
All of this series from Ingo pulled.
Looks fine so far, my only reaction is that "Ho humm, now Ingo is the
main -tip user who doesn't sign his pull requests". Both Thomas and
Borislav have started doing so.
Ingo? It shouldn't be that much extra work, it's an added "git tag
-s". You can even automate it, and just make the tag-name be the
branch name plus a date/time thing, and it will probably fit in
whatever scripting you do now.
Yeah, it does result in that password prompt, so it's not _entirely_
invisible, although that might be minimized with pgp-agent.
I know you have a key, since I have it in my chain. Of course, the key
I have for you is from 2011, maybe you've lost it.
I'd love to be at the point where all the major pulls I do are signed.
But no, this still isn't a requirement for kernel.org users, more of a
"please consider it".
Thanks,
Linus
On Tue, Mar 31, 2020 at 3:03 AM Ingo Molnar <mingo@kernel.org> wrote:
>
> Linus,
>
> Please pull the latest x86-vmware-for-linus git tree from:
...
next prev parent reply other threads:[~2020-03-31 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 10:03 [GIT PULL] x86/vmware changes for v5.7 Ingo Molnar
2020-03-31 19:11 ` Linus Torvalds [this message]
2020-04-02 8:15 ` Ingo Molnar
2020-03-31 19:15 ` 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-=wim0vZMxgxmu=eW4pCqExbcJqswEvK=VYuyqkB-40koTg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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).