From: Ondrej Zary <linux@rainbow-software.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] e-mail clients
Date: Fri, 8 Sep 2006 18:06:49 +0200 [thread overview]
Message-ID: <200609081806.50087.linux@rainbow-software.org> (raw)
In-Reply-To: <200609080918.47693.gene.heskett@verizon.net>
On Friday 08 September 2006 15:18, Gene Heskett wrote:
> On Friday 08 September 2006 08:54, Hans-Peter Jansen wrote:
> >Am Freitag, 8. September 2006 10:24 schrieb Jesper Juhl:
> >> On 08/09/06, Victor Hugo <victor@vhugo.net> wrote:
> >> > 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 about which client to use on lkml?? Pine?? Mutt??
> >> > Thunderbird?? Telnet??
> >>
> >> I personally use both 'pine' and 'kmail' and they both work perfectly
> >> for sending patches.
> >
> >With kmail, you have control over line breaks with Option -> Wrap lines,
> >which is useful for e.g. pasted syslog data, but remember to enable it
> >before writing the message, since you have to manually add line breaks
> >for the entered text too.
> >
> >Inlined patches should be added via Message -> Insert File to preserve
> >line breaks and white space.
>
> But be sure and turn word wrapping off before inserting the file, or
> pasting (usually bad I might add). And my version of kmail wraps the
> whole document if the wrapping is turned back on, as it is now. Which
> makes it rather frustrating.
To workaround this, I first type the message with wordwrapping on, then close
the message window and let it save the message to Drafts. Then repoen the
message from Drafts, turn off wordwrap and insert the patch using
Message->Insert File. It's not great but still better than Thunderbird.
>
> >Pete
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> > in the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at http://www.tux.org/lkml/
--
Ondrej Zary
next prev parent reply other threads:[~2006-09-08 16:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 0:02 [RFC] e-mail clients Victor Hugo
2006-09-08 7:13 ` Jan Engelhardt
2006-09-08 7:24 ` Michal Piotrowski
2006-09-08 8:17 ` Jan Engelhardt
2006-09-08 8:31 ` Michal Piotrowski
2006-09-08 9:05 ` Jan Engelhardt
2006-09-08 22:54 ` Pavel Machek
2006-09-08 8:24 ` Jesper Juhl
2006-09-08 10:29 ` Rafael J. Wysocki
2006-09-08 12:54 ` Hans-Peter Jansen
2006-09-08 13:18 ` Gene Heskett
2006-09-08 16:04 ` Vadim Lobanov
2006-09-08 16:06 ` Ondrej Zary [this message]
2006-09-08 14:05 ` Alistair John Strachan
2006-09-08 20:03 ` LKML FAQ, newsgroups and newbies (was Re: [RFC] e-mail clients) Oleg Verych
2006-09-08 8:47 ` [RFC] e-mail clients Paolo Ornati
2006-09-08 10:54 ` Stefan Richter
2006-09-08 14:53 ` Brice Goglin
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 3:32 Randy Dunlap
2006-09-12 7:08 ` Jan Engelhardt
2006-09-12 12:58 ` Stefan Richter
2006-09-12 17:34 ` Segher Boessenkool
2006-09-12 23:16 ` Randy.Dunlap
2006-09-12 15:41 ` Lee Revell
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=200609081806.50087.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=gene.heskett@verizon.net \
--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