linux-kernel - Re: linux-next: Tree for Feb 27

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: <20080228100618.3eb58692.sfr@canb.auug.org.au>
Date:	Thu, 28 Feb 2008 10:06:18 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Theodore Tso <tytso@....EDU>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Feb 27

Hi Ted,

On Wed, 27 Feb 2008 14:55:25 -0500 Theodore Tso <tytso@....EDU> wrote:
>
> please add:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git  next

Added, thanks.

> This contains a subset of the patches in the ext4 patch set which we
> are explicitly planning on pushing to Linus at the next merge window.

That's what we want.

> It actually probably wouldn't hurt to pull the entire quilt series
> into linux-next, since we don't export any interfaces that are used by
> other linux trees, and that would give us better heads up for
> conflicts in patches still in development conflicting with upcoming
> core changes.  But it conflicts with the initial premise of
> linux-next, so that's why I set up the next branch of the above git
> tree.

Thanks, the less conflicts I have to fix the better.  :-)  I guess over
time patches will migrate into your next branch or they will appear there
after the next Linus release.

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

Content of type "application/pgp-signature" skipped