From: Ralf Baechle <ralf@linux-mips.org>
To: Sergei Shtylylov <sshtylyov@ru.mvista.com>
Cc: Martin Michlmayr <tbm@cyrius.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [PATCH] Au1xx0: OHCI region size off-by-one
Date: Wed, 22 Mar 2006 12:01:05 +0000 [thread overview]
Message-ID: <20060322120105.GB4544@linux-mips.org> (raw)
In-Reply-To: <441F5147.6000509@ru.mvista.com>
On Tue, Mar 21, 2006 at 04:05:11AM +0300, Sergei Shtylylov wrote:
> >... and please post your patches inline rather than as MIME
> >attachments. :)
>
> My mailer will stuff tabs with spaces then, and I know text/plain
> attachments are considered OK.
Well, the topic isn't new but here is some wisdom from others on how to
post patches with the various wannabe mail clients like Mozilla.
Quoting from Alan Cox:
> For Evolution
>
> Set the formatting to "Preformat"
> Hit Insert/Text File (Alt-I X)
> Then at the ghastly gnome dialog hit ^L (secret handshake for the
> 'developers cant stand it either' shortcut box) and type in the file
> name
And here some wisedom from Randy Dunlap on Thunderbird:
>> Randy D. eventually agreed that there was a way, IIRC:
>>
>> http://lkml.org/lkml/2005/12/27/191
>>
>> Probably can work your way through the thread to figure out how (I use mutt :)
> Yep, the odd part is not to disable html email.
> Then when composing a message, there is a drop-down box for a format
> selection. While the cursor is in the body area, change the format
> from default "Body text" to Preformat, and then copy-n-paste the patch.
> At least that's what worked for me.
And Frank Sorenson:
> Here is one method for posting patches in Thunderbird:
>
> Before starting to write the email, do Edit->Preferences, Composition
> tab, change "Wrap plain text messages at __ characters" to 0
>
> Begin writing your email
>
> Start up an editor in which you can select the text, for example:
> # gvim patch.diff
> Edit->Select All
> Edit->Copy
>
> Switch back to the open Compose window, then Edit->Paste
>
> If you have Enigmail configured, when sending the email, you might get a
> box asking if you want to change the line wrapping to 68 characters, so
> just say No if that happens.
Others have suggested using an external editor which will show up in the
compose editor and allow to include the patch file inline.
Here's Martin Bligh's page on the topic:
http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
Credits for anybody would writes some useful docs for the linux-mips wiki
on this topic - unfortunately it's really high in demand. I'd do it
myself - but I am a mutt + vi user :-)
Ralf
next prev parent reply other threads:[~2006-03-22 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 0:54 [PATCH] Au1xx0: OHCI region size off-by-one Sergei Shtylylov
2006-03-21 1:02 ` Martin Michlmayr
2006-03-21 1:05 ` Sergei Shtylylov
2006-03-22 12:01 ` Ralf Baechle [this message]
2006-05-25 18:47 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2006-03-20 23:38 Sergei Shtylylov
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=20060322120105.GB4544@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
--cc=tbm@cyrius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.