public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Either trim quoted text or STOP BOTTOM POSTING
Date: Fri, 25 Aug 2017 14:25:00 -0000	[thread overview]
Message-ID: <f5667926-a166-e766-9fb3-ed0bccb2f5d1@gmail.com> (raw)
In-Reply-To: <599F710B.1070306@tlinx.org>

On 8/24/2017 8:36 PM, L A Walsh wrote:
> If you can't trim your quoted text, then please stop burying the
> new stuff on the bottom.
> 

Did you wake up on the wrong side of the bed.  I see from a google
search that you've had problems with style in the past even on this list.

> 
> I've noticed it is most often bottom-poster who include all
> previous quotes -- and that's the worst -- having to WADE
> through EVERYTHING that came before, when EVERYONE on the
> list has already received it.  That's the rub: if you

List etiquette frowns on both bottom and top posting and warrants to
interleaving the replies.

> want to bottom-post, then trim what you are quoting to that
> which is necessary (and that's fine w/me).
> But if you are not good about trimming, then put the *IMPORTANT*
> stuff first (your NEW text).  That's write -- the most important
s/write/right
> thing in your email is what YOU are writing.  It should come
> first.  If you feel a need to quote large parts of the previous
> conversation, put it in an appendix -- because most people will
> have already received and read it.  Including it again is
> "superfluous", but that's why there are appendices.

What I'm replying to follows what I'm quoting to give context to the
reply.  My reply should never be more important that the reason for the
response.  Without the context of what I'm responding to there is no
reason to reply but I should create a new subject and thread.

> 
> I DO pay attention to the subject BTW.

Well all and good but you hijacked a thread to bring home a point which
is in itself just wrong.

https://wiki.openstack.org/wiki/MailingListEtiquette

-- 
cyg Simple

--
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

  reply	other threads:[~2017-08-25 14:25 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             ` cyg Simple [this message]
2017-08-25 16:43               ` Either trim quoted text or STOP BOTTOM POSTING Dan Kegel
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=f5667926-a166-e766-9fb3-ed0bccb2f5d1@gmail.com \
    --to=cygsimple@gmail.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).