From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271812AbTGXXIZ (ORCPT ); Thu, 24 Jul 2003 19:08:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271813AbTGXXIZ (ORCPT ); Thu, 24 Jul 2003 19:08:25 -0400 Received: from tmr-02.dsl.thebiz.net ([216.238.38.204]:23819 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id S271812AbTGXXIV (ORCPT ); Thu, 24 Jul 2003 19:08:21 -0400 Date: Thu, 24 Jul 2003 19:15:23 -0400 (EDT) From: Bill Davidsen To: "Robert L. Harris" cc: Steven Cole , linux-kernel@vger.kernel.org, Tomas Szepe Subject: Re: Posting format In-Reply-To: <20030724154732.GJ32585@rdlg.net> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/SIGNED; MICALG=pgp-sha1; PROTOCOL="application/pgp-signature"; BOUNDARY=VkqCAaSJIySsbD6j Content-ID: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --VkqCAaSJIySsbD6j Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: On Thu, 24 Jul 2003, Robert L. Harris wrote: > 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. I tried to make the point that top posting is useful when (and only when) it is short and does not require the context of the previous posts, it saves the reader time to have it all up front. Example 1: Subject: 2.6.0-test2-ac1 OOPS with ZIP and DVD Appropriate top post: Fixed in 2.6.0-test2-ac2 Why: Topic is dead, problem over, casual reader spends no more time on it Example 2: Subject: Odd O(1) behaviour with SCSI tape and serial PPP Appropriate top post: The measurements Jonas requested appear below interspersed with his questions. Why: If you want details you won't miss this post, if you are only concerned with patches or discussion of root cause you might skip this one. A short top post takes the place of the Summary header most folks can't generate or see. Used properly it's a benefit, used as the examples Thomas posted it's disgusting. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. --VkqCAaSJIySsbD6j Content-Type: APPLICATION/PGP-SIGNATURE Content-ID: Content-Description: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/H/+U8+1vMONE2jsRAkVtAJ9CuXhH9QJUiVLyDG1vLuO10x69gwCfaXHx 5LG3mXzwFOIvpVX95wbAPH0= =QKst -----END PGP SIGNATURE----- --VkqCAaSJIySsbD6j--