linux-kernel - Re: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded

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: <200711140809.51644.a1426z@gawab.com>
Date:	Wed, 14 Nov 2007 08:09:51 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	Valdis.Kletnieks@...edu
Cc:	Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded

Valdis.Kletnieks@...edu wrote:
> On Tue, 13 Nov 2007 19:42:10 +0300, Al Boldi said:
> > Oh.  What about breaking out a stable-mm snapshot against the latest
> > stable kernel?
>
> You can roll your own of those.
>
> Get a 2.6.23.N kernel tarball.
> patch -R the 23.N patch against that, giving you a 23.0 tree.
> Apply patch-2.6.24-rc2 to that.
>
> Now apply the snapshot.

Ok, but I was thinking of allowing a more selective approach.  First, break 
out an mm snapshot that only contain patch-sets that are deemed stable, but 
still not ready for rc.  Then, a tool may allow to selectively apply a 
specific patch-set against the latest stable kernel, not the rc.  This could 
possibly improve longer-term testing, instead of just relying on crunch-time 
rc testing.

Thanks!

--
Al

-
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/