From: Dan Carpenter <dan.carpenter@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: Re: [lustre-devel] [patch] Staging: lustre: indent an if statement
Date: Fri, 14 Oct 2016 11:52:47 +0000 [thread overview]
Message-ID: <20161014115247.GG5687@mwanda> (raw)
In-Reply-To: <3ea7f15f-4f53-c303-3c38-064432cb599c@hlrs.de>
On Fri, Oct 14, 2016 at 12:36:25PM +0200, Martin Hecht wrote:
> On 10/14/2016 12:38 AM, James Simmons wrote:
> >> This if statement wasn't intended.
> just to be sure: in conjunction with the subject of the mail this should
> read "indented" instead of "intended", right?
Yes, yes. I should just avoid both words from now on because my fingers
constantly get mixed up.
Greg already applied this so it's too late to send a v2.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [patch] Staging: lustre: indent an if statement
Date: Fri, 14 Oct 2016 14:52:47 +0300 [thread overview]
Message-ID: <20161014115247.GG5687@mwanda> (raw)
In-Reply-To: <3ea7f15f-4f53-c303-3c38-064432cb599c@hlrs.de>
On Fri, Oct 14, 2016 at 12:36:25PM +0200, Martin Hecht wrote:
> On 10/14/2016 12:38 AM, James Simmons wrote:
> >> This if statement wasn't intended.
> just to be sure: in conjunction with the subject of the mail this should
> read "indented" instead of "intended", right?
Yes, yes. I should just avoid both words from now on because my fingers
constantly get mixed up.
Greg already applied this so it's too late to send a v2.
regards,
dan carpenter
next prev parent reply other threads:[~2016-10-14 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:52 [patch] Staging: lustre: indent an if statement Dan Carpenter
2016-10-13 8:52 ` [lustre-devel] " Dan Carpenter
2016-10-13 22:38 ` James Simmons
2016-10-13 22:38 ` [lustre-devel] " James Simmons
2016-10-14 10:36 ` Martin Hecht
2016-10-14 10:36 ` Martin Hecht
2016-10-14 11:52 ` Dan Carpenter [this message]
2016-10-14 11:52 ` Dan Carpenter
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=20161014115247.GG5687@mwanda \
--to=dan.carpenter@oracle.com \
--cc=lustre-devel@lists.lustre.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.