From: Mark Lord <liml@rtr.ca>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix translation for START STOP UNIT
Date: Tue, 30 Jan 2007 19:38:35 -0500 [thread overview]
Message-ID: <45BFE50B.7040103@rtr.ca> (raw)
In-Reply-To: <45BF57EA.6060201@shaw.ca>
Robert Hancock wrote:
> Jeff Garzik wrote:
>> * Include the patch inline rather than as an attachment.
..
>
> 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
Yup, major nuisance. I have to fire up Kmail whenever I'm posting patches,
and then go back to Thunderbird again afterwards.
Cheers
next prev parent reply other threads:[~2007-01-31 0:38 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
2007-01-31 0:38 ` Mark Lord [this message]
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=45BFE50B.7040103@rtr.ca \
--to=liml@rtr.ca \
--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).