From: Lee Revell <rlrevell@joe-job.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: hotfixes for -mm kernels
Date: Thu, 02 Feb 2006 15:53:52 -0500 [thread overview]
Message-ID: <1138913633.15691.109.camel@mindpipe> (raw)
In-Reply-To: <200602021502_MC3-1-B772-547@compuserve.com>
On Thu, 2006-02-02 at 15:00 -0500, Chuck Ebbert wrote:
> Most -mm kernels have small but critical bugs that are found shortly
> after release. Patches for these are posted on linux-kernel but
> they aren't made available on kernel.org until the next -mm release.
>
> Would it be possible to create a hotfix/ directory for each -mm
> release and put those patches there? A README could explain that
> the fixes are untested. At least people reading the files could
> see an issue exists even if they're not brave enough to try the
> patch. :)
I doubt it - mm is an experimental kernel, hotfixes only make sense for
production stuff. It moves too fast.
A better question is what does -mm give you that mainline does not, that
causes you to want to "stabilize" a specific -mm version?
Lee
next prev parent reply other threads:[~2006-02-02 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 20:00 Wanted: hotfixes for -mm kernels Chuck Ebbert
2006-02-02 20:53 ` Lee Revell [this message]
2006-02-02 21:45 ` Dmitry Torokhov
2006-02-02 21:48 ` Randy.Dunlap
2006-02-02 21:57 ` Dmitry Torokhov
2006-02-03 10:07 ` Marc Koschewski
2006-02-04 16:37 ` Martin J. Bligh
2006-02-04 18:57 ` Marc Koschewski
2006-02-04 19:22 ` Martin J. Bligh
2006-02-05 8:56 ` Marc Koschewski
2006-02-04 20:41 ` Adrian Bunk
2006-02-05 9:09 ` Marc Koschewski
2006-02-05 15:13 ` Adrian Bunk
2006-02-05 2:56 ` Paul Jackson
2006-02-05 8:58 ` Marc Koschewski
2006-02-05 15:58 ` Martin J. Bligh
2006-02-05 17:15 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2006-02-02 22:08 Chuck Ebbert
2006-02-02 22:29 ` Andrew Morton
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=1138913633.15691.109.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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