linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Chuck Ebbert <76306.1226@compuserve.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges (was:	[MAILER-DAEMON@rumms.u
Date: Wed, 09 Apr 2003 11:34:01 -0600	[thread overview]
Message-ID: <194120000.1049909641@aslan.btc.adaptec.com> (raw)
In-Reply-To: <1049886804.9901.19.camel@dhcp22.swansea.linux.org.uk>

> On Mer, 2003-04-09 at 02:21, Chuck Ebbert wrote:
>> And your code goes for long periods of time without merging good fixes,
>> like this one (from 2.4.20):
> 
> Which is one reason Justin's patches don't get merged. They are giant
> changes which back out other clear corrections.

This tells me two things:

1) You don't trust maintainers.  If a maintainer can't make large changes,
   who can?

2) When a maintainer makes a mistake (fails to integrate a good change,
   or introduces a bug), the maintainers changes are simply dropped rather
   then notify (either politely or not I don't much care) the maintainer
   of his/her mistake.

Neither of the above applied to integration of the aic79xx driver into
the 2.4.X tree, but it still took something like 8 months.

There must be a better way.

--
Justin


  reply	other threads:[~2003-04-09 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  1:21 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Chuck Ebbert
2003-04-09  2:13 ` Justin T. Gibbs
2003-04-09 11:13 ` Alan Cox
2003-04-09 17:34   ` Justin T. Gibbs [this message]
2003-04-10 11:20     ` [PATCH] aic7* claims all checked EISA io ranges Stephan von Krawczynski
2003-04-10 16:44       ` Justin T. Gibbs
2003-04-11  8:51         ` Stephan von Krawczynski
2003-04-11 11:39         ` Stephan von Krawczynski
2003-04-09 22:10 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u Chuck Ebbert
2003-04-10  1:48 ` carbonated beverage

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=194120000.1049909641@aslan.btc.adaptec.com \
    --to=gibbs@scsiguy.com \
    --cc=76306.1226@compuserve.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).