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.
On 2/20/06, Alexey Dobriyan <[email protected]> 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
>
I may be wrong, but to the best of my knowledge that's not possible.
I tried for a while to get it to do that exactely so I could tell
people using it how to do it, but I gave up.
I'd say the best solution is to use a different MUA. 'pine', 'mutt',
'kmail' or even just plain 'mail' from a commandline works well.
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
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.
Evolution has an option for setting the Content-Disposition: inline
header on individual attachments; I haven't seen the same option in
thunderbird.
Sam.
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
Oh, give it up...
> Sending plain text attachments is OK with me, but, heh, people do post
> patches inline and screw themselves.
Personally I'd simply advocate plain text attachments. One thing though;
if you are going to, please make note of the long (long) standing bug in
TB that has it send all attachments (including plaintext ones) Base64
encoded when the outgoing encoding is set to UTF-8.
I do normally have outgoing set to UTF-8 and for example forgot to
disable that earlier today when I sent an OOPS as an attachment. You
don't immediately notice this yourself, since TB simply decodes it again
when viewing...
Rene.
On 2/20/06, Alexey Dobriyan <[email protected]> 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.
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 :)
Thanks,
Nish
On Monday 20 February 2006 21:12, Sam Vilain wrote:
> 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.
>
> Evolution has an option for setting the Content-Disposition: inline
> header on individual attachments; I haven't seen the same option in
> thunderbird.
Many clients have this feature, although it does not end up being presented by
the client as quotable text. Read: any form of attachment is suboptimal.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
On Tue, 2006-02-21 at 10:12 +1300, Sam Vilain wrote:
> 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.
>
> Evolution has an option for setting the Content-Disposition: inline
> header on individual attachments; I haven't seen the same option in
> thunderbird.
>
> Sam.
Even better, you can inline plain text in Evolution if you switch the
text style to "Preformat" just before going to the "Insert" menu,
selecting "Text file...", and selecting a file to insert. This works
even with HTML-formatted output turned off in your preferences.
Cheers,
-Matt Helsley
On Mon, 20 Feb 2006 13:30:59 -0800 Nish Aravamudan wrote:
> On 2/20/06, Alexey Dobriyan <[email protected]> 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.
>
> 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.
---
~Randy
Rene Herman wrote:
> Personally I'd simply advocate plain text attachments. One thing though;
> if you are going to, please make note of the long (long) standing bug in
> TB that has it send all attachments (including plaintext ones) Base64
> encoded when the outgoing encoding is set to UTF-8.
No attachments at all, please...
Jeff
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.
>
Attaching the .diff file works correctly right? You are just saying
some people try to paste the text inline and so it gets line wrapped?
On Llu, 2006-02-20 at 21:34 +0000, Alistair John Strachan wrote:
> On Monday 20 February 2006 21:12, Sam Vilain wrote:
> > Evolution has an option for setting the Content-Disposition: inline
> > header on individual attachments; I haven't seen the same option in
> > thunderbird.
>
> Many clients have this feature, although it does not end up being presented by
> the client as quotable text. Read: any form of attachment is suboptimal.
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
-----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
[email protected]
-----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-----
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.
>
I've been sending patches inline with thunderbird. Most important setting
is "wrap plain text messages at 0 characters".
Getting the external editor extension makes the job much easier. It allows
you to use your favorite editor while in the compose window.
Tony
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.
http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
M.
On 2/21/06, Martin Bligh <[email protected]> wrote:
> http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
Eek. I'd recommend using xclip [1] rather than using a mouse to cut
from emacs/whatever. ( xclip <my.diff , then paste in Thunderbird.)
[1] http://people.debian.org/~kims/xclip/
Ray
Ray Lee wrote:
> On 2/21/06, Martin Bligh <[email protected]> wrote:
>
>>http://mbligh.org/linuxdocs/Email/Clients/Thunderbird
>
>
> Eek. I'd recommend using xclip [1] rather than using a mouse to cut
> from emacs/whatever. ( xclip <my.diff , then paste in Thunderbird.)
>
> [1] http://people.debian.org/~kims/xclip/
Nice. Or rather ... slightly less foul than before. Wiki duly updated.
The whole thing still sucks ass, but still. Someone needs to smack
the thunderbird people with a 30lb wet salmon.
Thanks for the pointer.
M.