mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Marc Koschewski <marc@osknowledge.org>
Cc: dtor_core@ameritech.net, rlrevell@joe-job.com,
	76306.1226@compuserve.com, akpm@osdl.org,
	linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: Wanted: hotfixes for -mm kernels
Date: Sat, 4 Feb 2006 08:37:52 -0800	[thread overview]
Message-ID: <20060204083752.a5c5b058.mbligh@mbligh.org> (raw)
In-Reply-To: <20060203100703.GA5691@stiffy.osknowledge.org>


> > > 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. ;)

Why do people always thing a source code control system is magically going
to fix all bugs and wipe their ass for them?

You still have to work out which patches are relevant and merge them. If 
he's just merging a new set of changes constantly, it won't help you a damn. 

What is needed is somebody to do the grunt work, not SCM magic. I'll try to
help with Randy's suggestion of a shared pool of patches in a common dumping 
ground at least - I've needed pretty much the same thing in the past for the 
test.kernel.org stuff ... mainly fixups needed to get the tree to boot so
we can test it.

M.

  reply	other threads:[~2006-02-04 16:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02 20:00 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
2006-02-04 16:37       ` Martin J. Bligh [this message]
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
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=20060204083752.a5c5b058.mbligh@mbligh.org \
    --to=mbligh@mbligh.org \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@osknowledge.org \
    --cc=rdunlap@xenotime.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®