linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: V9FS Developers <v9fs-developer@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: [GIT PULL] 9p updates for 4.19
Date: Fri, 17 Aug 2018 09:37:05 -0700	[thread overview]
Message-ID: <CA+55aFzLe7C03-53=0WrXXfZcfsJfTsvRqrrBNqnLvOxUiCJqQ@mail.gmail.com> (raw)
In-Reply-To: <20180817023307.GA32726@nautica>

So this pull request confuses me, and that's not a good thing.

On Thu, Aug 16, 2018 at 7:33 PM Dominique Martinet
<asmadeus@codewreck.org> wrote:
>
> Pull request for inclusion in 4.19 for 9p

So when I pull the tag, I get a different message, talking about

  This tag is the same as 9p-for-4.19 without the two MAINTAINERS patches

but I never saw a first version.

And it comes from a github address, with a pgp key that I've not seen
before, and without me having been told about said maintainership
updates. And while the  key has a lot of signatures, none of them are
any that I have recognized previously from kernel development.

I'm sure it's all ok, but honestly, there's no way I can pull this
without a bit more clarification.

             Linus

  reply	other threads:[~2018-08-17 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180813012347.GA32555@nautica>
2018-08-17  2:33 ` [GIT PULL] 9p updates for 4.19 Dominique Martinet
2018-08-17 16:37   ` Linus Torvalds [this message]
2018-08-17 21:36     ` Dominique Martinet
2018-08-17 22:35       ` Linus Torvalds
2018-08-17 22:41         ` Andrew Morton
2018-08-17 23:41           ` Linus Torvalds
2018-08-18  0:31             ` 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='CA+55aFzLe7C03-53=0WrXXfZcfsJfTsvRqrrBNqnLvOxUiCJqQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=asmadeus@codewreck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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).