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

On Thu, 2003-07-24 at 09:47, Robert L. Harris wrote:
> 
> Thus spake Steven Cole (elenstev@mesatop.com):

[snippage]
> > 
> > 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

Using a consistent agglutination policy results in more easily
understandable conversations.  You've done a good job advocating top
posting, but until recently the linux-kernel norm was bottom posting.

The mix of the two is what is being objected to.  Standards exist for
good reasons, and Tomas pointed out RFC 1855 and the lkml FAQ.

Please reply at the bottom.  Thanks.

Steven


  parent reply	other threads:[~2003-07-24 15:55 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
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 [this message]
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=1059062739.1668.214.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=Robert.L.Harris@rdlg.net \
    --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).