From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: coding style: use linux kernel style for indentation
Date: Wed, 13 Jan 2016 08:49:59 -0800 [thread overview]
Message-ID: <20160113084959.797beea5@xeon-e3> (raw)
In-Reply-To: <20160113150708.GD7756@bricha3-MOBL3>
On Wed, 13 Jan 2016 15:07:08 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:
> So, while the two-tab indent may look "a bit weird" it does solve the two issues
> above. I believe practical benefits should override initial impressions. [It took
> me a while to get used to also, but now I very much like it as a style.]
I don't think that deviating from kernel style for this case is justified.
next prev parent reply other threads:[~2016-01-13 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 7:58 Yuanhan Liu
2016-01-13 15:07 ` Bruce Richardson
2016-01-13 16:49 ` Stephen Hemminger [this message]
2018-02-13 12:51 ` Ferruh Yigit
2018-02-13 13:12 ` Yuanhan Liu
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=20160113084959.797beea5@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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).