public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, Andre Hedrick <andre@linux-ide.org>
Subject: Re: Dropped patches
Date: Sat, 15 Dec 2001 19:19:37 -0500	[thread overview]
Message-ID: <20011215191937.B30548@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10112151049260.13398-100000@master.linux-ide.org> <3C1BA20B.48FF8735@mandrakesoft.com>
In-Reply-To: <3C1BA20B.48FF8735@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sat, Dec 15, 2001 at 02:18:35PM -0500

On Sat, Dec 15, 2001 at 02:18:35PM -0500, Jeff Garzik wrote:
> Andre Hedrick wrote:
> > Well blame that on the folks that are not taking kernel code that will
> > allow you to solve this problem.  Linus is the number one offender.
> 
> Linus is taking some patches and not others right now...  so what?  A
> couple of my patches, isolated and clearly unrelated to bio and mochel's
> driver work, made it in.  Others got dropped.

Patches that are unrelated to bio and obviously correct shouldn't be dropped 
indefinately, or if they're being deferred, then $maintainer should say so.

> I do not believe this as a personal condemnation of your patches, or
> bcrl's, or anyone else's.
> 
> Patience is a virtue ;-)   We have a long devel series in front of us
> and we are only at the pre-patches to the FIRST 2.5.x release.

There is no reason not to have a 6 month devel cycle, and plenty of reasons 
in favour of it.  If people aren't going to bother reviewing patches in a 
timely fashion, they should tell people when a good time to resend patches 
is.  Given the whole vm fiasco in 2.4 (which is still a mess and falling 
apart for heavy loads) which stems from a lot of random direction with 
patches, I hope that some of the underlying problems will get fixed.  But 
it really doesn't look that way.

		-ben
-- 
Fish.

  parent reply	other threads:[~2001-12-16  0:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 17:35 PDC20265 IDE controller trouble Jurij Smakov
2001-12-15 17:56 ` Rene Rebe
     [not found]   ` <Pine.LNX.4.33.0112151309350.19022-100000@coffee.psychology.mcmaster.ca>
2001-12-15 18:40     ` Rene Rebe
2001-12-15 18:52   ` Andre Hedrick
2001-12-15 19:18     ` Dropped patches Jeff Garzik
2001-12-15 23:41       ` Dropped patches -> dropped bugfix 2.4 since months ! Gunther Mayer
2001-12-15 23:12         ` Andre Hedrick
2001-12-16  0:19       ` Benjamin LaHaise [this message]
2001-12-15 20:27     ` PDC20265 IDE controller trouble Rene Rebe

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=20011215191937.B30548@redhat.com \
    --to=bcrl@redhat.com \
    --cc=andre@linux-ide.org \
    --cc=jgarzik@mandrakesoft.com \
    --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