e-mail clients
Quoted 7 lines
As I've learned--most web-clients have a hard time sending text only e-mail without
wrapping every single line (not very good for patches). Any
suggestions
Quoted 2 lines
about which client to use on lkml?? Pine?? Mutt??
Thunderbird?? Telnet??
pine (but make sure that it doesn't truncate trailing whitespace) or mutt or sylpheed are all good. tbird can be coerced into working but it's not much fun (well, using attachments is easy, but not good for people when reviewing/commenting on patches).
---
~Randy
Quoted 2 lines
pine (but make sure that it doesn't truncate trailing whitespace)
Truncating whitespace at EOL is a good thing. Otherwise, quilt says
Warning: trailing whitespace in lines 237,364 of net/ipv4/netfilter/regexp/regexp.c
Warning: trailing whitespace in line 57 of net/ipv4/netfilter/regexp/regsub.c
Warning: trailing whitespace in lines 307,308,309 of net/ipv4/netfilter/ipt_layer7.c
for example. Long lines are usually not broken up if pasted verbatim as this example line will show for sure abc.
pine wraps text only when typing (at least that's how I configured mine), so it is all safe.
Jan Engelhardt
Quoted 3 lines · Jan Engelhardt
Quoted 1 line
pine (but make sure that it doesn't truncate trailing whitespace)
Truncating whitespace at EOL is a good thing.
[...]
Trailing whitespace should be removed before generating the patch, not while sending the patch.
Signature · 3 lines
Stefan Richter -=====-=-==- =--= -==-- http://arcgraph.de/sr/
Quoted 6 lines · Randy Dunlap
Quoted 6 lines
As I've learned--most web-clients have a hard time sending text only e-mail without
wrapping every single line (not very good for patches). Any
Quoted 8 lines
suggestions
Quoted 2 lines
about which client to use on lkml?? Pine?? Mutt??
Thunderbird?? Telnet??pine (but make sure that it doesn't truncate trailing whitespace) or mutt or sylpheed are all good. tbird can be coerced into working but it's not much fun (well, using attachments is easy, but not good for people when reviewing/commenting on patches).
It's easy to post correct patches with Evolution...
Lee
Quoted 5 lines
Quoted 1 line
Truncating whitespace at EOL is a good thing.
[...]
Trailing whitespace should be removed before generating the patch, not while sending the patch.
And not even then, when the patch is removing trailing whitespace :-)
Segher
Quoted 11 lines · On Tue, 12 Sep 2006 09:08:37 +0200 (MEST) Jan Engelhardt wrote:
Quoted 2 lines
pine (but make sure that it doesn't truncate trailing whitespace)
Truncating whitespace at EOL is a good thing. Otherwise, quilt says
Warning: trailing whitespace in lines 237,364 of
net/ipv4/netfilter/regexp/regexp.c
Warning: trailing whitespace in line 57 ofnet/ipv4/netfilter/regexp/regsub.c
Warning: trailing whitespace in lines 307,308,309 ofnet/ipv4/netfilter/ipt_layer7.c
Of course. But there were/are versions of pine that truncate whitespace "for you," even if such truncation is not desired, independent of quilt et al. So one wouldn't want to use that "feature" for kernel patches.
Quoted 4 lines
for example. Long lines are usually not broken up if pasted verbatim as this example line will show for sure abc.
pine wraps text only when typing (at least that's how I configured mine), so it is all safe.
---
~Randy