From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: state of the nfsd tree
Date: Thu, 6 Jan 2022 21:55:06 -0500 [thread overview]
Message-ID: <20220107025506.GA16601@fieldses.org> (raw)
In-Reply-To: <20220107134621.7814487b@canb.auug.org.au>
On Fri, Jan 07, 2022 at 01:46:21PM +1100, Stephen Rothwell wrote:
> 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.
Sounds like a good idea to me.
> 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?
Probably so.
--b.
next prev parent reply other threads:[~2022-01-07 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:46 linux-next: state of the nfsd tree Stephen Rothwell
2022-01-07 2:55 ` J. Bruce Fields [this message]
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=20220107025506.GA16601@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.