From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
marcelo@conectiva.com.br
Subject: Re: Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released
Date: Thu, 23 Jan 2003 21:54:37 -0700 [thread overview]
Message-ID: <756820000.1043384077@aslan.scsiguy.com> (raw)
In-Reply-To: <20030123.202727.102788332.davem@redhat.com>
> And in fact, you are describing exactly what Linus and Marcelo's
> jobs are, to reject bogus/broken changes.
I think you missed the subtely of what I said. It's not "their duty"
to never make a mistake, and it is not expected that they will catch
everything. When they do miss something, or make a mistake you probably
tell them in a straight forward fashion. In this case, what you
effectively said to me was:
"Hey. I would appreciate it if you would stop not
noticing this change that I made to your code through
Linus without telling you. *Twice* no less. Wake up!
Wasn't it obvious? It is *your duty* to notice these
one line changes that happen to break the build on
a platform that I care about but doesn't have any
consequences on the platforms you are probably testing.
Oh, and the aic79xx driver... well I didn't bother to
look at that because it's not in my configuration.
Oh well."
And I get all of this grief *after* I already included the change
instead of after the first time I missed it. You really make me
laugh!
--
Justin
next prev parent reply other threads:[~2003-01-24 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 22:50 Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released Justin T. Gibbs
2003-01-23 12:14 ` Denis Vlasenko
2003-01-23 15:08 ` Justin T. Gibbs
2003-01-24 3:55 ` David S. Miller
2003-01-24 3:45 ` Justin T. Gibbs
2003-01-24 3:35 ` David S. Miller
2003-01-24 3:56 ` Justin T. Gibbs
2003-01-24 3:53 ` David S. Miller
2003-01-24 4:26 ` Justin T. Gibbs
2003-01-24 4:27 ` David S. Miller
2003-01-24 4:54 ` Justin T. Gibbs [this message]
2003-01-24 4:58 ` David S. Miller
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=756820000.1043384077@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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