From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: state of the nfsd tree
Date: Fri, 7 Jan 2022 13:46:21 +1100 [thread overview]
Message-ID: <20220107134621.7814487b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Hi all,
I noticed commit
a71baee992c6 ("MAINTAINERS: remove bfields")
in the cel tree and was sondering if I shuld remove the nfsd tree
(git://git.linux-nfs.org/~bfields/linux.git#nfsd-next) from linux-next.
Maybe I sould rename the cel tree
(git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux#for-next)
to be the nfsd treeas well?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-01-07 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:46 Stephen Rothwell [this message]
2022-01-07 2:55 ` linux-next: state of the nfsd tree J. Bruce Fields
2022-01-07 3:13 ` Chuck Lever III
2022-01-08 6:52 ` Stephen Rothwell
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=20220107134621.7814487b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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