From: Dan Kegel <dank@kegel.com>
To: cygwin@cygwin.com
Subject: Re: Either trim quoted text or STOP BOTTOM POSTING
Date: Fri, 25 Aug 2017 16:43:00 -0000 [thread overview]
Message-ID: <CAPF-yObk2aRg4HvQaUZMpUAjbv1biuw3_oFRqYKhw23M25P0Dw@mail.gmail.com> (raw)
In-Reply-To: <f5667926-a166-e766-9fb3-ed0bccb2f5d1@gmail.com>
I hadn't heard the name 'interleaved' style, I think that used to be
called top-posting plus appropriate trimming.
I sympathize with folks who are frustrated with whippersnappers not
knowing email conventions.
(It's almost as bad as not knowing how to use a manual gearshift :-)
- Dan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-08-25 16:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 22:30 alias appears to not work inside a called bash script Michel LaBarre
2017-08-21 22:53 ` Eliot Moss
2017-08-21 22:55 ` alias appears to not work inside a called bash scripty Duncan Roe
2017-08-22 1:01 ` Michel LaBarre
2017-08-22 14:31 ` alias appears to not work inside a called bash script Stephen John Smoogen
2017-08-22 14:47 ` Eliot Moss
2017-08-22 15:19 ` Stephen John Smoogen
2017-08-22 16:46 ` Eliot Moss
2017-08-22 18:25 ` Stephen John Smoogen
2017-08-25 0:37 ` Either trim quoted text or STOP BOTTOM POSTING (was: alias appears to not work...) L A Walsh
2017-08-25 14:25 ` Either trim quoted text or STOP BOTTOM POSTING cyg Simple
2017-08-25 16:43 ` Dan Kegel [this message]
2017-08-26 6:04 ` convenient trimming of quoted text to make points L A Walsh
2017-08-26 15:26 ` cyg Simple
2017-09-01 4:54 ` Duncan Roe
2017-09-01 7:37 ` Csaba Raduly
2017-09-01 12:38 ` cyg Simple
2017-08-22 17:08 ` alias appears to not work inside a called bash script cyg Simple
2017-08-22 17:14 ` Eliot Moss
2017-08-22 19:07 ` cyg Simple
2017-08-22 19:11 ` cyg Simple
2017-08-23 19:08 ` Eric Blake
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=CAPF-yObk2aRg4HvQaUZMpUAjbv1biuw3_oFRqYKhw23M25P0Dw@mail.gmail.com \
--to=dank@kegel.com \
--cc=cygwin@cygwin.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).