public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: charles-heselton@cox.net,
	Dieter N?tzel <Dieter.Nuetzel@hamburg.de>,
	Dan Mann <mainlylinux@attbi.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	"J.A. Magallon" <jamagallon@able.es>
Subject: Re: Kernel 2.5.6 Interactive performance
Date: 10 Mar 2002 01:05:55 -0500	[thread overview]
Message-ID: <1015740391.858.44.camel@phantasy> (raw)
In-Reply-To: <20020310043854.GA311@matchmail.com>
In-Reply-To: <NFBBKFIFGLNJKLMMGGFPKEPDCFAA.charles-heselton@cox.net> <1015734229.858.4.camel@phantasy>  <20020310043854.GA311@matchmail.com>

On Sat, 2002-03-09 at 23:38, Mike Fedyk wrote:

> On Sat, Mar 09, 2002 at 11:23:48PM -0500, Robert Love wrote:
> > The 2.5 tree also has most of these toys, and is a better place for this
> > development IMO.  Personally, I'd stay away from these all-in-one silly
> > patches that are floating around these days.  Your safest bet is just
> > stock 2.4.18 or whatever is latest, although the above addons are all at
> > varying levels of "stable" and "safe".
> > 
> 
> Then what do you call -aa and -ac? ;)
> 
> These "all-in-one" patches do make it harder to debug specific patches, but
> it does create a wider audience for many patches that wouldn't be used
> otherwise.

I don't put -aa nor -ac in the same category as what I refer to above. 
Alan and Andrea's trees both contain an intelligent combination of
useful patches, bug fixes, and code from Alan and Andrea themselves.

The plethora of all-in-one every-patch-under-the-sun patchsets don't
fall into the above category, in my opinion.  They just mix various new
feature patches.  They do offer one benefit: much wider exposure for
some potentially very useful patches.  I have found, however, that they
don't help the actual patch authors much since (a) they are mixed in
with many other patches and possibly even erroneously merged and (b) the
bug reports never make it upstream to the actual patch maintainers.

Maybe I'm just annoyed by the even greater signal-to-noise ratio on lkml
:-)

	Robert Love


  reply	other threads:[~2002-03-10  6:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 19:55 Kernel 2.5.6 Interactive performance Dieter Nützel
2002-03-10  1:00 ` Charles Heselton
2002-03-10  1:11   ` Dieter Nützel
2002-03-10  1:15     ` Charles Heselton
2002-03-10  4:23       ` Robert Love
2002-03-10  4:38         ` Mike Fedyk
2002-03-10  6:05           ` Robert Love [this message]
2002-03-10  6:18             ` Charles Heselton
2002-03-10  4:55         ` J Sloan
2002-03-11  1:05     ` Andrea Arcangeli
     [not found] <003301c1c7fd$a67d08f0$bb187143@amer.cisco.com>
2002-03-10  7:23 ` Charles Heselton
  -- strict thread matches above, loose matches on Subject: below --
2002-03-08  0:14 2.5.6-3 -- preempt_schedule unresolved in snd-pcm.o, snd-emu10k1-synth.o and snd-emu10k1.o Miles Lane
2002-03-09 18:55 ` Kernel 2.5.6 Interactive performance Dan Mann

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=1015740391.858.44.camel@phantasy \
    --to=rml@tech9.net \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=charles-heselton@cox.net \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mainlylinux@attbi.com \
    --cc=mfedyk@matchmail.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