From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Ke Wei <kewei@marvell.com>, Ke Wei <kewei.mv@gmail.com>,
linux-scsi@vger.kernel.org, Michael Wang <qswang@marvell.com>,
Jacky Feng <jfeng@marvell.com>, Qun Zhao <qzhao@marvell.com>,
Larry Li <lil@marvell.com>,
saeed bishara <saeed.bishara@gmail.com>
Subject: Re: [PATCH] Marvell 6440 SAS/SATA driver
Date: Fri, 22 Feb 2008 10:38:08 -0600 [thread overview]
Message-ID: <1203698288.6206.25.camel@localhost.localdomain> (raw)
In-Reply-To: <47BEF7B1.1090905@garzik.org>
On Fri, 2008-02-22 at 11:26 -0500, Jeff Garzik wrote:
> 4) [major] Your email was encoded in base64, which makes it difficult
> for automated tools to handle, and difficult for some mail clients to
> view and reply-to.
Yes, I echo this, there's also another problem it causes: The email
didn't actually get through the scsi reflector in part, I suspect,
because of the base64 content (anybody who wasn't on the direct to or cc
list is only seeing Jeff's reply).
James
next prev parent reply other threads:[~2008-02-22 16:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FE3F06125A99254E8D92161AA4569C6F02310B1A@sc-exch02.marvell.com>
2008-02-22 16:26 ` [PATCH] Marvell 6440 SAS/SATA driver Jeff Garzik
2008-02-22 16:38 ` James Bottomley [this message]
[not found] <20080122151857.GA8680@ubuntu.domain>
2008-01-22 15:24 ` Ke Wei
2008-01-23 3:58 ` Jeff Garzik
2008-01-23 10:54 ` Ke Wei
2008-01-23 11:41 ` Jeff Garzik
2008-01-25 16:43 ` Ke Wei
2008-01-25 17:24 ` Grant Grundler
2008-01-25 17:38 ` James Bottomley
2008-01-25 22:12 ` Jeff Garzik
2008-01-25 17:38 ` Grant Grundler
2008-01-25 22:39 ` James Bottomley
2008-01-27 15:10 ` Ke Wei
2008-01-27 15:27 ` Ke Wei
2008-01-27 18:13 ` James Bottomley
2008-02-05 13:19 ` Ke Wei
2008-02-05 21:00 ` Luben Tuikov
2008-02-07 0:33 ` Jeff Garzik
2008-01-25 23:00 ` James Bottomley
2008-01-25 23:05 ` Jeff Garzik
2008-01-25 21:27 ` James Bottomley
2008-01-23 19:23 ` Grant Grundler
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=1203698288.6206.25.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=jeff@garzik.org \
--cc=jfeng@marvell.com \
--cc=kewei.mv@gmail.com \
--cc=kewei@marvell.com \
--cc=lil@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=qswang@marvell.com \
--cc=qzhao@marvell.com \
--cc=saeed.bishara@gmail.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