From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>,
Sanidhya Solanki <jpage.lkml@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: email-clients.txt
Date: Sun, 06 Dec 2015 10:11:04 -0800 [thread overview]
Message-ID: <1449425464.7417.7.camel@perches.com> (raw)
In-Reply-To: <20151206083037.2bde6e58@lwn.net>
On Sun, 2015-12-06 aASCIIt 08:30 -0700, Jonathan Corbet wrote:
> On Sun, 6 Dec 2015 01:09:39 -0500
> Sanidhya Solanki <jpage.lkml@gmail.com> wrote:
[]
> > Evolution (GUI)
> >
> > +As of December 2015, the composing & inserting method described below
> > +does not work.
>
> Could it really be that nobody is using evolution? Much nicer here would
> be to describe how it fails to work, and, ideally, come up with a fix.
Evolution 3.12 works fine.
The text editor for Evolution versions > 3.12 is broken
and unrepairable.
Evolution 3.16 has very poor behavior when replying to
text emails with tabs. A ">" character is added before
every tab in the reply.
Evolution 3.18 occasionally uses the Non-Breaking-Space
(NBSP) character instead of the standand ASCII 32 space
which breaks applying patches sent with that email client.
next prev parent reply other threads:[~2015-12-06 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 6:09 [PATCH] Documentation: email-clients.txt Sanidhya Solanki
2015-12-06 15:30 ` Jonathan Corbet
2015-12-06 18:11 ` Joe Perches [this message]
2015-12-06 18:13 ` Jonathan Corbet
2015-12-07 0:10 ` Sanidhya Solanki
2015-12-07 4:13 ` Joe Perches
2015-12-07 5:24 ` Randy Dunlap
2015-12-06 21:35 ` Paul Bolle
2015-12-06 21:40 ` Paul Bolle
2015-12-06 20:52 ` Randy Dunlap
2015-12-07 18:16 ` Austin S Hemmelgarn
-- strict thread matches above, loose matches on Subject: below --
2015-12-07 0:01 Sanidhya Solanki
2015-12-07 8:03 ` Clemens Ladisch
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=1449425464.7417.7.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=jpage.lkml@gmail.com \
--cc=linux-doc@vger.kernel.org \
--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