From: James Bottomley <James.Bottomley@steeleye.com>
To: Rusty Trivial Russell <trivial@rustcorp.com.au>
Cc: Justin Gibbs <gibbs@btc.adaptec.com>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Jens Axboe <axboe@suse.de>, John Cherry <cherry@osdl.org>
Subject: Re: [TRIVIAL] fix parallel builds for aic7xxx]
Date: 24 Sep 2003 09:10:52 -0500 [thread overview]
Message-ID: <1064412654.2063.3.camel@mulgrave> (raw)
In-Reply-To: <20030924032922.BE68C2C21F@lists.samba.org>
On Tue, 2003-09-23 at 21:56, Rusty Trivial Russell wrote:
> [ Sorry, did you guys end up with consensus on this? Should I forward
> or drop? Thanks, Rusty ]
Justin, I think after some discussion you agreed this to be correct.
I'll apply it unless I hear otherwise.
James
next prev parent reply other threads:[~2003-09-24 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 2:56 [TRIVIAL] fix parallel builds for aic7xxx] Rusty Trivial Russell
2003-09-24 12:36 ` Christoph Hellwig
2003-09-24 14:10 ` James Bottomley [this message]
2003-09-24 14:39 ` Justin T. Gibbs
2003-09-24 16:21 ` John Cherry
2003-09-26 4:20 ` Rusty Russell
2003-09-26 15:02 ` John Cherry
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=1064412654.2063.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=cherry@osdl.org \
--cc=gibbs@btc.adaptec.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-scsi@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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