From: Al Boldi <a1426z@gawab.com>
To: Valdis.Kletnieks@vt.edu
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded
Date: Wed, 14 Nov 2007 08:09:51 +0300 [thread overview]
Message-ID: <200711140809.51644.a1426z@gawab.com> (raw)
In-Reply-To: <5021.1194990201@turing-police.cc.vt.edu>
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
next prev parent reply other threads:[~2007-11-14 5:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 15:21 mm snapshot broken-out-2007-11-13-04-14.tar.gz uploaded Al Boldi
2007-11-13 15:26 ` Peter Zijlstra
2007-11-13 16:42 ` Al Boldi
2007-11-13 21:43 ` Valdis.Kletnieks
2007-11-14 5:09 ` Al Boldi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-13 12:15 akpm
2007-11-14 0:20 ` Kevin Winchester
2007-11-14 1:11 ` Andrew Morton
2007-11-14 1:15 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711140809.51644.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox