From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: ctree: added lines after variable declarations
Date: Mon, 22 Feb 2016 22:49:45 +0000 (UTC) [thread overview]
Message-ID: <pan$17dfe$67929ac1$28a8f2a0$663c45df@cox.net> (raw)
In-Reply-To: 20160222072210.GA17243@carbon.ljdarc.local
Philippe Loctaux posted on Mon, 22 Feb 2016 08:22:10 +0100 as excerpted:
> Oh okay, thanks :)
>
> On Sun, Feb 21, 2016 at 04:44:14PM -0800, Joe Perches wrote:
>> On Mon, 2016-02-22 at 01:31 +0100, Philippe Loctaux wrote:
>> > Hi,
>> > I'm really sorry, but I don't understand what you're trying to mean.
>> > Could you simplify your sentence please (since I'm not english
>> > native)?
>> > I'd really apreciate that, thanks :)
>>
>> Please do not put your reply at the top of the email. (top-post)
But... you still did it!
(OTOH, this is an example of replying in context, save for the small
problem that the message I replied to was top-posted, making things out
of order for readers both of this message and of further messages that
maintain the quotes in that order. Had you replied at the bottom, or
interleaved in context under each point you're replying to, further
replies and their context would have been far clearer for others reading
and replying.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2016-02-22 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 23:46 [PATCH] Btrfs: ctree: added lines after variable declarations Philippe Loctaux
2016-02-21 23:53 ` Joe Perches
2016-02-22 0:01 ` Philippe Loctaux
2016-02-22 0:06 ` Joe Perches
2016-02-22 0:31 ` Philippe Loctaux
2016-02-22 0:44 ` Joe Perches
2016-02-22 7:22 ` Philippe Loctaux
2016-02-22 22:49 ` Duncan [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='pan$17dfe$67929ac1$28a8f2a0$663c45df@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).