From: Adrian Bunk <bunk@stusta.de>
To: Marc Koschewski <marc@osknowledge.org>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
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: Sun, 5 Feb 2006 16:13:14 +0100 [thread overview]
Message-ID: <20060205151314.GD5271@stusta.de> (raw)
In-Reply-To: <20060205090959.GC5663@stiffy.osknowledge.org>
On Sun, Feb 05, 2006 at 10:09:59AM +0100, Marc Koschewski wrote:
> * Adrian Bunk <bunk@stusta.de> [2006-02-04 21:41:39 +0100]:
> > On Sat, Feb 04, 2006 at 07:57:39PM +0100, Marc Koschewski wrote:
>...
> > > We talked about hotfixes for -mm. So why not check these into the -mm-git tree
> > > then? This would make sense and would conform fully to my understanding of what
> > > the -mm-git tree should be. I don't want to select 23 patches from LKML to make
> > > the tree compile or work. I want to checkout. Why make it easy when you may get
> > > it difficult.
> > >...
> > > What sense does an -mm tree make when there are people that cannot test it because of
> > > known bugs that lead to the -mm tree not being bootable or - even worse - destroying
> > > the system?
> >
> > That's exactly what Andrew does now implement through the hot-fixes
> > directory [1].
>...
> Moreover, just _one_ more thing which is most important at least to me:
> If one can do a checkout on a daily basis with let's say 3 new patches checked
> in, one can test these. The other day there are maybe another 2 new patches
> applied which are to be tested. This would just speed up the testing cycle
> whereas a 3 MB patch with tons of fixes and testing is just like a kick-down
> with the hand-brake pulled. Sometimes I#M really overwhelmed by how many patches
> came in with the recent -mm. ACPI, ALSA, VM, various FS stuff, ... It's quite
> impossible to me to really test the patches in an effective manner due to having
> my 2 eyes focussed on too many things at one. I do test ALSA with various types
> of in/out operation while my reiserfs partition is on the way to hell. To me
> that doesn't sound like effective testing.
>
> This is just about testing and debugging time effectiveness and not about some
> religious thing a la SCM vs. patches.
Hotfixes are something that can be done.
What you suggest is not really possible.
Your thinko is:
3 new patches a day don't sum up to 3 MB after one week.
As far as I understand it, the big work for Andrew is integrating two
dozen git repositories and at about thousand patches in a way that:
- everything applies
- the kernel compiles on several architectures
- the kernel actually runs on some machines
Andrew does all this before he releases an -mm kernel (I know due to the
feedback he sometimes gives for patches I sent), and this is the sole
reason why most -mm kernels are half-way usable.
Some random snapshot from Andrew's repository wouldn't help anyone,
either it's good enough that he releases an -mm kernel or it isn't worth
other people testing it.
> Marc
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-05 15:13 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
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 [this message]
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=20060205151314.GD5271@stusta.de \
--to=bunk@stusta.de \
--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=mbligh@mbligh.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