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

Date:	Wed, 27 Feb 2008 14:55:25 -0500
From:	Theodore Tso <tytso@....EDU>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
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

On Thu, Feb 28, 2008 at 01:06:26AM +1100, Stephen Rothwell wrote:
> On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > So who's missing now?

> > ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/

Hi Stephen,

please add:

   git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git  next

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.

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.

Regards,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/