public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: On why bottom posting....
Date: Fri, 09 May 2014 12:13:00 -0000	[thread overview]
Message-ID: <536CC670.2040406@etr-usa.com> (raw)
In-Reply-To: <536C25B4.8050504@tlinx.org>

On 5/8/2014 18:47, Linda Walsh wrote:
>
> They don't realize

Hasty generalization fallacy.  You don't know what they realize.

> like most good sources, will put the historical context information
> at the end in an appendix.

This is either the no true Scotsman fallacy, or denying the antecedent. 
  "My AP History teacher made us cite sources like this, therefore 
people who don't do it that way are wrong."

Most email is conversation, not essay or article writing.  The only 
reason we need quotes at all is that the pieces of the conversation are 
spaced apart in time and space, so we need context to keep the pieces 
strung together.

> Now if we can just get the bottom-posters to realize that by posting
> the footnotes, historical data, and duplicate info at the top
> of the document, they are more likely to lose the reader who is
> only scanning the first half the page.

That's why bottom-posting is supposed to go along with aggressive quote 
trimming, so that the quote includes only the pithiest possible 
reference to the prior contribution to the conversation.

I *have* noticed a lot of emails to the Cygwin lists with the entire 
prior conversation seemingly quoted, and one or two sentences appended. 
  If you want to rail against that, I'm right there with you.

  parent reply	other threads:[~2014-05-09 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <536796E4.2090009@breisch.org>
     [not found] ` <20140505135928.GK30918@calimero.vinschen.de>
     [not found]   ` <53679D5C.5030209@breisch.org>
     [not found]     ` <20140505144745.GA6993@calimero.vinschen.de>
     [not found]       ` <5367ACED.40409@breisch.org>
     [not found]         ` <20140505154230.GB7694@calimero.vinschen.de>
     [not found]           ` <5367B990.8050907@breisch.org>
     [not found]             ` <20140505165723.GM30918@calimero.vinschen.de>
     [not found]               ` <5367DEE5.5010407@breisch.org>
     [not found]                 ` <5367EA1F.3060800@cygwin.com>
     [not found]                   ` <5368094E.7040806@breisch.org>
     [not found]                     ` <53680C04.6050609@cygwin.com>
2014-05-09  0:48                       ` Linda Walsh
2014-05-09  1:41                         ` Christopher Faylor
2014-05-09 12:13                         ` Warren Young [this message]
2014-05-09 15:23                           ` Christopher Faylor
2014-05-09 19:44                           ` Linda Walsh
2014-05-09 20:26                             ` Christopher Faylor
2014-05-12 16:59                             ` Warren Young

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=536CC670.2040406@etr-usa.com \
    --to=warren@etr-usa.com \
    --cc=cygwin-talk@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).