linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Steven Cole <elenstev@mesatop.com>
Cc: bill davidsen <davidsen@tmr.com>,
	linux-kernel@vger.kernel.org, Tomas Szepe <szepe@pinerecords.com>
Subject: Re: Posting format
Date: Thu, 24 Jul 2003 11:47:32 -0400	[thread overview]
Message-ID: <20030724154732.GJ32585@rdlg.net> (raw)
In-Reply-To: <1059059667.1672.202.camel@spc9.esa.lanl.gov>

[-- Attachment #1: Type: text/plain, Size: 3246 bytes --]




Thus spake Steven Cole (elenstev@mesatop.com):

> On Wed, 2003-07-23 at 17:32, bill davidsen wrote:
> > A one or two line summary at the top of an article often saves the
> > reader from reading the entire thing.
> > 
> > In article <20030723225333.GC16244@louise.pinerecords.com>,
> > Tomas Szepe  <szepe@pinerecords.com> wrote:
> [snipped]
> > | 
> > | Would you people please stop replying above the original messages?
> > | 
> > | One could say this evil (pioneered by certain silly mail clients btw)
> > | has been spreading like plague around here lately.
> > | 
> > | Quoting the lkml FAQ ->
> > | (REG) And please reply after the quoted text, not before it (as per RFC
> > | 1855).  It's very confusing to see a reply before the quoted context.
> > 
> [snipped]
> > 
> > |                                                                   And
> > | it's embarrassing: it makes you look like a newbie.  Change your mailer if
> > | necessary, if the one you have makes it hard to do reply-after-quoting.
> > | I know some people like to quote the entire message they are replying to,
> > | so they put their reply right at the top so people won't give up after the
> > | first page of quoted material.  Don't do it.  It's annoying.  Just learn to
> > | stop quoting everything.  No-one wants to see it all anyway (list archives
> > | allow people to see everything if they missed it).  You're not helping
> > | yourself anyway, as you're more likely to be ignored if you
> > | reply-before-quoting.
> > 
> > Seriously, you have a point, but his two liner did not require the
> > context of the bulk of the post. There have been some far worse choices
> > of top posting, and the main reason for not top posting is because it's
> > hard to read *when context is needed*.
> > 
> > Your point is good, I think you could have picked a number of better
> > examples to make it.
> 
> More exposition regarding top vs bottom posting: Replying at the bottom
> results in an easily parseable tree. Consider the following conversation
> where everyone replies at the bottom.


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.  You could read just the top post and go from there.
For those new to the conversation they can just start at the bottom and
scroll up.  When the next post comes in they just read the top post
again instead of scrolling down to the bottom or middle somewhere to
figure out what/when/where.

Using VI and Mutt, the cursor starts at the top not the bottom or
anywhere in the middle so there's and ease of use for CLI mail readers
as well instead of the GUI oriented.


:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu 
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Diagnosis: witzelsucht  	

IPv6 = robert@ipv6.rdlg.net	http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net	http://www.rdlg.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-24 15:32 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 [this message]
2003-07-24 16:03             ` Tomas Szepe
2003-07-24 16:52               ` Steven Cole
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=20030724154732.GJ32585@rdlg.net \
    --to=robert.l.harris@rdlg.net \
    --cc=davidsen@tmr.com \
    --cc=elenstev@mesatop.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).