From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] nfsd bugfixes for 4.2
Date: Wed, 5 Aug 2015 15:49:18 -0400 [thread overview]
Message-ID: <20150805194918.GB18809@fieldses.org> (raw)
In-Reply-To: <CA+55aFyh=hT8id4LOgVhrE7GTGtgqRCtfCewhm83yLcFEYQPxg@mail.gmail.com>
On Wed, Aug 05, 2015 at 11:01:53AM +0200, Linus Torvalds wrote:
> On Tue, Aug 4, 2015 at 11:09 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > Please pull a few nfsd bugfixes for 4.2 from:
>
> Pulled. However, I wonder if you could start making signed tag pull
> requests. I don't know how linux-nfs.org is maintained, and it's
> probably all really good and private, but it still makes me go
> "Wouldn't it be nice if..."
OK! Apologies, I did at least get a key generated and signed by people
a few years ago, then I was too lazy to figure out how to use it. I'll
give it a go for the next pull request.
--b.
prev parent reply other threads:[~2015-08-05 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 21:09 [GIT PULL] nfsd bugfixes for 4.2 J. Bruce Fields
2015-08-05 9:01 ` Linus Torvalds
2015-08-05 19:49 ` J. Bruce Fields [this message]
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=20150805194918.GB18809@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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