From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] libata: fix translation for START STOP UNIT
Date: Wed, 31 Jan 2007 00:22:04 -0800 [thread overview]
Message-ID: <45C051AC.6060107@mbligh.org> (raw)
In-Reply-To: <45BF5984.1030508@garzik.org>
Jeff Garzik wrote:
> Robert Hancock wrote:
>> Jeff Garzik wrote:
>>> * Include the patch inline rather than as an attachment. Even a
>>> text/plain attachment is very difficult to review and quote in
>>> popular email programs.
>>>
>>> Jeff
>>
>> I'd love to, but unfortunately nobody seems to have come up with a way
>> of doing this in Thunderbird that keeps it from mangling whitespace
>> without a ton of hassle. I was able to get it to cooperate once (sort
>> of, anyway, I think it may have still damaged something on the first
>> try), but it required mangling a bunch of settings that made using it
>> for normal mail impossible.
>>
>> The last time I looked, the main "how-to" page I found had an addendum
>> that "I gave up on this, it's too hard, I just attach the patches". If
>> anyone has gotten any new insight..
>
> Just use "cat mail | sendmail -t" or git-send-email, Thunderbird will
> never get this stuff right.
>
> I'm fighting Thunderbird right this second, in fact, because it randomly
> decided to stop supporting drag-n-drop to sub-folders in Fedora Core 6 :(
http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
Describes how to fix this.
M.
next prev parent reply other threads:[~2007-01-31 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 1:29 [PATCH] libata: fix translation for START STOP UNIT Robert Hancock
2007-01-30 14:24 ` Jeff Garzik
2007-01-30 14:36 ` Robert Hancock
2007-01-30 14:43 ` Jeff Garzik
2007-01-31 8:22 ` Martin J. Bligh [this message]
2007-01-31 0:38 ` Mark Lord
2007-02-01 0:27 ` Tejun Heo
2007-02-01 1:04 ` Mark Lord
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=45C051AC.6060107@mbligh.org \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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).