lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 7 Jan 2022 03:13:58 +0000
From:   Chuck Lever III <chuck.lever@...cle.com>
To:     "J. Bruce Fields" <bfields@...ldses.org>
CC:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: state of the nfsd tree


> On Jan 6, 2022, at 9:55 PM, J. Bruce Fields <bfields@...ldses.org> wrote:
> 
> 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.

Both sound OK to me too.

Powered by blists - more mailing lists