From: Bill Davidsen <davidsen@tmr.com>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: linux <linux-kernel@vger.kernel.org>
Subject: Re: lock_kernel twice possible ?
Date: Wed, 19 Oct 2005 17:29:17 -0400 [thread overview]
Message-ID: <4356BAAD.2010409@tmr.com> (raw)
In-Reply-To: <2cd57c900510150047y4108a493k859f86bf1324468@mail.gmail.com>
Coywolf Qi Hunt wrote:
> On 10/15/05, li nux <lnxluv@yahoo.com> wrote:
>
>>Sorry, couldn't get what you want to say.
>>Can you please elaborate.
>
>
> http://www.zipworld.com.au/~akpm/linux/patches/stuff/top-posting.txt
> http://www.catb.org/~esr/jargon/html/T/top-post.html
The whole post fit on one screen and he was not continuing the
conversation, he was commenting on your post as a whole. I think you're
being a bit pedantic here.
I don't think his reply failed your criteria, it wasn't overlong, it
didn't break a flowing discussion, and no backward reading was required.
~~~~~~~
Q: Why is top-posting evil?
A1: Because top-posters tend to leave the entirety of the email to which
they are replying intact, so the email gets too long.
A2: Because we prefer to use bottom-posting, and it is *extremely* hard to
maintain a coherently flowing email conversation when some of the
participants are bottom-posting and some are top-posting.
A3: backwards read don't humans because
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-10-19 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 7:04 lock_kernel twice possible ? li nux
2005-10-15 7:33 ` Coywolf Qi Hunt
2005-10-15 7:38 ` li nux
2005-10-15 7:47 ` Coywolf Qi Hunt
2005-10-19 21:29 ` Bill Davidsen [this message]
2005-10-20 7:00 ` Steven Rostedt
2005-10-15 7:58 ` Mitchell Blank Jr
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=4356BAAD.2010409@tmr.com \
--to=davidsen@tmr.com \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.