From: Frank Sorenson <frank@tuxrocks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Mozilla Thunderbird posting instructions wanted
Date: Mon, 20 Feb 2006 16:46:41 -0700 [thread overview]
Message-ID: <43FA54E1.5060409@tuxrocks.com> (raw)
In-Reply-To: <20060220210349.GA29791@mipter.zuzino.mipt.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alexey Dobriyan wrote:
> This POS is pretty popular among kernel janitors, so, can someone who
> is successfully using it, please, post crystally clear step-by-step
> instructions on how to send a foo.patch:
> inline
> with tabs preserved
> with long lines preserved
>
> Sending plain text attachments is OK with me, but, heh, people do post
> patches inline and screw themselves.
>
> I'll put instructions somewhere on -kj website and point every
> unsuspecting new guy to them.
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.
Ideally, there would be a Thunderbird plugin to insert the contents of a
file at the current location with no formatting changes... Maybe "next
week" :)
Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFD+lTgaI0dwg4A47wRArxSAKCMsAj2SFckK2uPLdgTD4tHItqsHACg2eaN
nvwTg9GfO65nHahjS1MKrA4=
=0Eif
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-02-20 23:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 21:03 Mozilla Thunderbird posting instructions wanted Alexey Dobriyan
2006-02-20 21:12 ` Sam Vilain
2006-02-20 21:34 ` Alistair John Strachan
2006-02-20 23:11 ` Alan Cox
2006-02-20 22:11 ` Posting Patches with Evolution (WAS Re: Mozilla Thunderbird posting instructions wanted) Matt Helsley
2006-02-20 21:12 ` Mozilla Thunderbird posting instructions wanted Jesper Juhl
2006-02-20 21:25 ` Rene Herman
2006-02-20 22:22 ` Jeff Garzik
2006-02-20 21:30 ` Nish Aravamudan
2006-02-20 22:20 ` Randy.Dunlap
2006-02-20 22:31 ` Phillip Susi
2006-02-20 23:46 ` Frank Sorenson [this message]
2006-02-21 0:07 ` Antonino A. Daplas
2006-02-22 1:12 ` Martin Bligh
2006-02-22 1:49 ` Ray Lee
2006-02-22 1:57 ` Martin Bligh
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=43FA54E1.5060409@tuxrocks.com \
--to=frank@tuxrocks.com \
--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