linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u
Date: Wed, 9 Apr 2003 18:10:02 -0400	[thread overview]
Message-ID: <200304091812_MC3-1-33BC-8ED8@compuserve.com> (raw)


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


 I was wondering about that too.

 How can a major code restructure be done in tiny pieces?  I don't
think it can.


--
 Chuck
 I am not an octal number!

             reply	other threads:[~2003-04-09 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 22:10 Chuck Ebbert [this message]
2003-04-10  1:48 ` [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.u carbonated beverage
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09  1:21 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

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=200304091812_MC3-1-33BC-8ED8@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=gibbs@scsiguy.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;
as well as URLs for NNTP newsgroup(s).