From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block changes for 4.16-rc
Date: Mon, 29 Jan 2018 13:17:11 -0700 [thread overview]
Message-ID: <2f01d9a7-2788-00d2-c41f-11b9d6b991b0@kernel.dk> (raw)
In-Reply-To: <CA+55aFx3-2CFC_0BXtMC3kQ+nW_6aK2etyMi1AJks1m5z2W=qA@mail.gmail.com>
On 1/29/18 1:14 PM, Linus Torvalds wrote:
> On Mon, Jan 29, 2018 at 12:08 PM, Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Yes of course, I can switch to using signed tags for pull requests
>> for you.
>
> Thanks. I don't actually know the maintainership status of kernel.dk.
>
> You show up as the 'whois' contact, but I'm also assuming it doesn't
> have the same kind of fairly draconian access control as the
> kernel.org suite of sites, and I'm actively trying to make sure we
> either use signed tags or the kernel.org repos (and honestly, even
> with the kernel.org ones I tend to prefer signed tags).
>
> Right now I only _require_ it for public hosting, but I'm trying to
> move to just signed tags being the default everywhere.
The box is sitting right next to me in my office, which is locked. But
it's not kernel.org, and I don't have a dedicated sysadmin. My tree does
mirror to git.kernel.org, so they should be in sync (albeit with some
delay). If you're fine with signed tags on git.kernel.dk, I'd prefer
continue using that, but just signing the pull requests.
I sign all fio releases with the same key, so it'd be trivial for me to
just sign pulls as well.
--
Jens Axboe
next prev parent reply other threads:[~2018-01-29 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 15:40 [GIT PULL] Block changes for 4.16-rc Jens Axboe
2018-01-29 20:02 ` Linus Torvalds
2018-01-29 20:08 ` Jens Axboe
2018-01-29 20:14 ` Linus Torvalds
2018-01-29 20:17 ` Jens Axboe [this message]
2018-01-29 20:20 ` Linus Torvalds
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=2f01d9a7-2788-00d2-c41f-11b9d6b991b0@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@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