From: Al Boldi <a1426z@gawab.com>
To: Valdis.Kletnieks@vt.edu
Subject: Re: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded
Date: Wed, 14 Nov 2007 08:09:51 +0300
User-Agent: KMail/1.5
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
References: <200711131821.54056.a1426z@gawab.com> <200711131942.10195.a1426z@gawab.com> <5021.1194990201@turing-police.cc.vt.edu>
In-Reply-To: <5021.1194990201@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711140809.51644.a1426z@gawab.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1030
Lines: 31

Valdis.Kletnieks@vt.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/