linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: bill davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Posting format
Date: 24 Jul 2003 10:52:58 -0600	[thread overview]
Message-ID: <1059065578.1668.234.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <20030724160327.GB22052@louise.pinerecords.com>

On Thu, 2003-07-24 at 10:03, Tomas Szepe wrote:
> > [Robert.L.Harris@rdlg.net]
> > 
> > On the other hand if everyone posted at the top it would be considerably
> > easier reading for those who have been following the conversation
> > without having to scroll down and figure out where comments and the
> > conversation is at.
> 
> So how do you context-quote when replying at the top?
> 
> Original text:
> 
> 	Argument A.
> 	Argument B.
> 
> Reply:
> 
> 	Reply intro text.
> 
> 	Reaction A.
> 	> Argument A.
> 
> 	Reaction B.
> 	> Argument B.
> 
> I don't think so.  Awkward (mixing directions) and confusing.
> 
> > For those new to the conversation they can just start at the bottom and
> > scroll up.
> 
> Ever actually tried doing that?  IMHO it's not half as practical and
> natural as reading from the top down.  (You have to keep scrolling,
> searching for block starts.)

I think Tomas has just hit upon why top posting is fundamentally wrong.

Indo-European languages read left to right, Semitic languages read right
to left, and some Oriental languages read top to bottom, but no human
languages I'm aware of read bottom to top.  

Consider a Cafe sign:

C
a
f
e

That is readable.  How about:

e
f
a
C

Not very readable unless you spend extra processing time to think about
it. Reading bottom to top is counter-intuitive and wastes time. Speaking
of which, apologies to all who feel they've wasted time by reading this.

Hmm, it looks like you top-posters out there are in good company. 
Marcelo seems to be taking the lead.  Grumble.

Steven


  reply	other threads:[~2003-07-24 16:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 20:18 2.6.0-test1-ac3 still broken on Adaptec I2O Robert L. Harris
2003-07-23 20:22 ` Christoph Hellwig
2003-07-23 22:00   ` Robert L. Harris
2003-07-23 22:53     ` Tomas Szepe
2003-07-23 23:32       ` Posting format bill davidsen
2003-07-24  0:52         ` Tomas Szepe
2003-07-24 15:14         ` Steven Cole
2003-07-24 15:47           ` Robert L. Harris
2003-07-24 16:03             ` Tomas Szepe
2003-07-24 16:52               ` Steven Cole [this message]
2003-07-24 17:15                 ` Robert L. Harris
2003-07-24 17:42                   ` Steven Cole
2003-07-24 16:03             ` Bas Mevissen
2003-07-24 16:05             ` Steven Cole
2003-07-24 23:15             ` Bill Davidsen
2003-07-24 23:24             ` CaT
2003-07-25  2:59               ` jw schultz
2003-07-25  3:33                 ` Miles Bader
2003-07-24 15:24         ` [OT] " Sean Neakums
2003-07-23 20:24 ` 2.6.0-test1-ac3 still broken on Adaptec I2O Alan Cox
2003-07-23 21:20   ` Samuel Flory
2003-07-23 22:17     ` Alan Cox
2003-07-24  8:01       ` Christoph Hellwig
2003-07-24 11:24         ` Alan Cox
2003-07-24 17:37 Posting format Mudama, Eric
2003-07-24 18:57 John Bradford
2003-07-25 18:49 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-25 20:35 John Bradford
2003-07-25 22:10 ` jw schultz

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=1059065578.1668.234.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szepe@pinerecords.com \
    --subject='Re: Posting format' \
    /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

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 NNTP newsgroup(s).