linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org, Tomas Szepe <szepe@pinerecords.com>
Subject: Re: Posting format
Date: 24 Jul 2003 09:14:28 -0600	[thread overview]
Message-ID: <1059059667.1672.202.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <bfn5v6$m20$1@gatekeeper.tmr.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.

-------------------------------
To: hackerlist@webe.hackers.org
From: Delta <delta@cando.com>
Subj: foo.c does not compile, what to do?

Charlie wrote:
> Able wrote:
> > Baker wrote:
> > > Able wrote:
> > > > Baker wrote:
> > > > > Able wrote:
> > > > > > My driver foo.c does not compile. What can I do?
> > > > > > 
> > > > > > Able
> > > > > > 
> > > > > It hasn't been ported yet.  
> > > > > 
> > > > > Baker
> > > > > 
> > > > I really really need this.
> > > > 
> > > > Able
> > > > 
> > > Well then, either fix it yourself or find someone who can.
> > > 
> > > Baker
> > > 
> > But I can't fix it myself.  I don't know how.
> > 
> > Able
> > 
> I think Delta worked on this last year.  Delta, can you help?
> 
> Charlie
> 
Yeah I looked at that thing and ran away screaming.  Good luck.

Delta
-------------

Now, look at the same conversation where Able replies at the top.

-------------------------------
To: hackerlist@webe.hackers.org
From: Delta <delta@cando.com>
Subj: foo.c does not compile, what to do?

Charlie wrote:
> Able wrote:
> > But I can't fix it myself.  I don't know how.
> >
> > Able
> >
> > Baker wrote:
> > > Able wrote:
> > > > I really really need this.
> > > >
> > > > Able
> > > >
> > > > Baker wrote:
> > > > > Able wrote:
> > > > > > My driver foo.c does not compile. What can I do?
> > > > > > 
> > > > > > Able
> > > > > > 
> > > > > It hasn't been ported yet.
> > > > > 
> > > > > Baker
> > > > > 
> > > > 
> > > Well then, either fix it yourself or find someone who can.
> > > 
> > > Baker
> > > 
> > 
> I think Delta worked on this last year.  Delta, can you help?
> 
> Charlie
> 
Yeah I looked at that thing and ran away screaming.  Good luck.

Delta
-------------

The result is a tangled mess.  Untangling that mess wastes time.

Replying at the top wastes people's time trying to understand the
conversation.

For a theoretical discussion of why mixing top and bottom agglutination
is wrong, Steven Pinker's "The Language Instinct" has a chapter on how
differing languages build up trees.  Some add from the left, some from
the right, but arbitrarily mixing the two in the same sentence either
results in an ambiguity or what he calls "fruit salad".

Please reply at the bottom.

Steven




  parent reply	other threads:[~2003-07-24 15:04 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 [this message]
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
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=1059059667.1672.202.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).