All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Koschewski <marc@osknowledge.org>
To: dtor_core@ameritech.net
Cc: Lee Revell <rlrevell@joe-job.com>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: hotfixes for -mm kernels
Date: Fri, 3 Feb 2006 11:07:04 +0100	[thread overview]
Message-ID: <20060203100703.GA5691@stiffy.osknowledge.org> (raw)
In-Reply-To: <d120d5000602021345i255bb69eydb67bc1b0a448f8d@mail.gmail.com>

* Dmitry Torokhov <dmitry.torokhov@gmail.com> [2006-02-02 16:45:52 -0500]:

> On 2/2/06, Lee Revell <rlrevell@joe-job.com> wrote:
> > 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?
> >
> 
> Some people just run -mm so the hotfixes/* would help them to get
> their boxes running until the next -mm without having to hunt through
> LKML for bugs already reported/fixed. This will allow better testing
> coverage because most obvious bugs are caught almost immediately and
> then people can continue using -mm to find more stuff.

... that's just why I so often wish to have a -git tree, Andrew. ;)

Marc

  parent reply	other threads:[~2006-02-03 10:07 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
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 [this message]
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=20060203100703.GA5691@stiffy.osknowledge.org \
    --to=marc@osknowledge.org \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.