From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
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: Sat, 8 Jan 2022 17:52:03 +1100 [thread overview]
Message-ID: <20220108175203.705695f8@canb.auug.org.au> (raw)
In-Reply-To: <8F605496-7EB6-42A5-8C44-0A541EB2E402@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Hi all,
On Fri, 7 Jan 2022 03:13:58 +0000 Chuck Lever III <chuck.lever@oracle.com> wrote:
>
> > On Jan 6, 2022, at 9:55 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> >
> > On Fri, Jan 07, 2022 at 01:46:21PM +1100, Stephen Rothwell wrote:
> >>
> >> 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.
>
> Both sound OK to me too.
OK, both changes will happen from Monday.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-01-08 6:52 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
2022-01-07 3:13 ` Chuck Lever III
2022-01-08 6:52 ` Stephen Rothwell [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=20220108175203.705695f8@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