From: Jens Axboe <axboe@suse.de>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: marcelo@conectiva.com.br, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: cciss updates for 2.4.22-pre3 [1 of 6]
Date: Fri, 11 Jul 2003 09:20:28 +0200 [thread overview]
Message-ID: <20030711072028.GB843@suse.de> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF104052A5D@cceexc23.americas.cpqcorp.net>
On Thu, Jul 10 2003, Miller, Mike (OS Dev) wrote:
> These patches can be installed in any order EXCEPT the final 2 of the
> 6. They are name p1* & p2* respectively.
Mike, the 6 patches all look fine to me. However, your mailer has
screwed them up. There are random line breaks in there. For (partly, at
least) broken mailers, attachments are sometimes more reliable.
--
Jens Axboe
next parent reply other threads:[~2003-07-11 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D4CFB69C345C394284E4B78B876C1CF104052A5D@cceexc23.americas.cpqcorp.net>
2003-07-11 7:20 ` Jens Axboe [this message]
2003-07-11 12:52 ` cciss updates for 2.4.22-pre3 [1 of 6] Marcelo Tosatti
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=20030711072028.GB843@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mike.miller@hp.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;
as well as URLs for NNTP newsgroup(s).