From: Khem Raj <raj.khem@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Patrick Ohly <patrick.ohly@intel.com>
Cc: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: Re: truncating quoted text in emails
Date: Wed, 16 Nov 2016 10:08:34 -0800 [thread overview]
Message-ID: <8dacb506-b9e2-4e0f-96d5-5fb267301f5d@gmail.com> (raw)
In-Reply-To: <CADkTA4Pti3PEn7C1AWcy0H0RrWfjphSC1+396tp16z2Wm5PWww@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1079 bytes --]
On 11/16/16 9:01 AM, Bruce Ashfield wrote:
>
>
> On Wed, Nov 16, 2016 at 10:36 AM, Patrick Ohly <patrick.ohly@intel.com
> <mailto:patrick.ohly@intel.com>> wrote:
>
> Hello!
>
> While trying to follow patch reviews on this list I noticed that
> (subjectively?) quite a few replies completely quote the original email
> and then just add a few lines. That looks fine in GMail where the quoted
> text is folded, but not so much in mail readers where quoted text is
> unfolded (Evolution).
>
> A random example:
> http://lists.openembedded.org/pipermail/openembedded-core/2016-November/128861.html
> <http://lists.openembedded.org/pipermail/openembedded-core/2016-November/128861.html>
>
> Not sure what the netiquette is for this list, but at least I would
> appreciate a bit more aggressive trimming in replies - thanks! ;-}
>
>
>
> We might as well try to agree on an editor to use ;)
I would expect the users to be aware and do the needed. Worst case
your email wont be read or replied to.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-11-16 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 15:36 truncating quoted text in emails Patrick Ohly
2016-11-16 17:01 ` Bruce Ashfield
2016-11-16 18:08 ` Khem Raj [this message]
2016-11-16 22:17 ` Paul Eggleton
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=8dacb506-b9e2-4e0f-96d5-5fb267301f5d@gmail.com \
--to=raj.khem@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
/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