public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth (Conduent)" <Kenneth.Nellis@conduent.com>
To: Eric Blake <eblake@redhat.com>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: suggest adding posting dates to follows-up and references
Date: Wed, 22 Feb 2017 16:31:00 -0000	[thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A704BBEEDEB@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <d728c14c-d964-1b7f-4fe7-8801ca94ac81@redhat.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1387 bytes --]

From: Eric Blake 
> On 02/22/2017 08:27 AM, Nellis, Kenneth (Conduent) wrote:
> > FWIW, here's a change that I would find beneficial:
> >
> > At the bottom of a post, which is either a reply and/or has a follow-up,
> > we see something like the following example:
> >
> >  • Follow-Ups:
> 
> I'm guessing that you are using a webmail interface.  Such text is NOT
> part of the email body being sent, but is rather it is added by your
> webmail provider interpreting the <In-Reply-To> headers present on the
> message.  Other mail clients have their own way of showing threads.  But
> your request is not something the Cygwin list can change, but rather a
> feature you'd have to request from your webmail provider (or that you
> can change by downloading your emails and reading them with a local
> client like thunderbird or mutt).

No, I'm not using webmail. I am using browser to read postings directly
from http://cygwin.com/ml/cygwin. (I copied from the web page,
then pasted and did a bit of editing to get the bullets to render
somewhat before posting. Maybe that gave the appearance of what 
webmail might do.)

--Ken



\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2017-02-22 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 14:27 Nellis, Kenneth (Conduent)
2017-02-22 14:44 ` Eric Blake
2017-02-22 16:31   ` Nellis, Kenneth (Conduent) [this message]
2017-02-22 16:38     ` Eric Blake
2017-02-22 17:01       ` Nellis, Kenneth (Conduent)
2017-02-22 17:24         ` Eric Blake
2017-02-22 17:32           ` Nellis, Kenneth (Conduent)
2017-02-22 18:36             ` Andrew Schulman
2017-02-22 21:11               ` Erik Soderquist
2017-02-22 21:44                 ` Brian Inglis

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=0D835E9B9CD07F40A48423F80D3B5A704BBEEDEB@USA7109MB022.na.xerox.net \
    --to=kenneth.nellis@conduent.com \
    --cc=cygwin@cygwin.com \
    --cc=eblake@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).