From: Joao Correia <joaomiguelcorreia@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] Increase lockdep limits: MAX_LOCK_DEPTH
Date: Tue, 7 Jul 2009 16:46:48 +0100 [thread overview]
Message-ID: <a5d9929e0907070846w95f60b1nf278e3a1beb22cbd@mail.gmail.com> (raw)
In-Reply-To: <1246981272.9777.9.camel@twins>
On Tue, Jul 7, 2009 at 4:41 PM, Peter Zijlstra<a.p.zijlstra@chello.nl> wrote:
>
> A: Because we read from top to bottom, left to right.
> Q: Why should I start my reply below the quoted text?
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>
> A: The lost context.
> Q: What makes top-posted replies harder to read than bottom-posted?
>
Interesting :-).
Ill keep that in mind, apologies.
Joao Correia
prev parent reply other threads:[~2009-07-07 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:25 Joao Correia
2009-07-07 15:29 ` Peter Zijlstra
2009-07-07 15:36 ` Joao Correia
2009-07-07 15:41 ` Peter Zijlstra
2009-07-07 15:46 ` Joao Correia [this message]
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=a5d9929e0907070846w95f60b1nf278e3a1beb22cbd@mail.gmail.com \
--to=joaomiguelcorreia@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®