archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Konstantin Komarov <>
	linux-fsdevel <>,
	Linux Kernel Mailing List <>
Subject: Re: [GIT PULL] ntfs3: new NTFS driver for 5.15
Date: Sat, 4 Sep 2021 10:34:14 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Sep 3, 2021 at 8:19 AM Konstantin Komarov
<> wrote:
> master

Oh, I didn't notice this until now, as I was lining up to actually pull this.

I probably forgot to say this originally:

For github accounts (or really, anything but where I can
just trust the account management), I really want the pull request to
be a signed tag, not just a plain branch.

In a perfect world, it would be a PGP signature that I can trace
directly to you through the chain of trust, but I've never actually
required that.

So while I prefer to see a full chain of trust, I realize that isn't
always easy to set up, and so at least I want to see an "identity"
that stays constant so that I can see that pulls come from the same
consistent source that controls that key.

(We've also had situations where the chain of trust just didn't exist
_yet_, but then later on it can be established as a developer ends up
becoming more integral in the community)

Signed tags are easy to use - the hardest part is having any pgp key
setup at all, then git makes using the keys trivial with "git tag -s


  reply	other threads:[~2021-09-04 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 15:19 Konstantin Komarov
2021-09-04 17:34 ` Linus Torvalds [this message]
2021-09-04 18:08   ` Linus Torvalds
2021-09-04 19:00 ` 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] ntfs3: new NTFS driver for 5.15' \

* 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
on how to clone and mirror all data and code used for this inbox