linux-kernel - Re: linux-next: fate of the ecryptfs tree

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] [day] [month] [year] [list]

Message-Id: <20120602133703.be8c52b85b17b25b074aac8e@canb.auug.org.au>
Date:	Sat, 2 Jun 2012 13:37:03 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Tyler Hicks <tyhicks@...onical.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: fate of the ecryptfs tree

Hi Tyler,

On Fri, 1 Jun 2012 16:41:55 -0700 Tyler Hicks <tyhicks@...onical.com> wrote:
>
> On 2012-05-31 14:41:15, Stephen Rothwell wrote:
> > 
> > I am just wondering about the fate of the ecryptfs tree.  The most recent
> > commit to that tree is dated Feb 11 and seems to have been included in
> > Linus' tree as a different commit.
> 
> My next branch has become stale. Sorry about that! I haven't been doing
> much development on the kernel side in the last couple months. That will
> soon change, as I have a few bug fixes in the works and I know of a
> contribution or two that should surface shortly.

Thanks for that.

> In the meantime, I've just pushed the HEAD of Linus' tree to my next
> branch to clean things up.

Excellent.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped