From: Jerin Jacob <jerinjacobk@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH RFC] devtools: increase default line length to 100
Date: Tue, 9 Jun 2020 10:12:03 +0530 [thread overview]
Message-ID: <CALBAE1NufwR+FuzJNFV5G6dvaNiCGHW-r12CqxyKHoqwtW7CpA@mail.gmail.com> (raw)
In-Reply-To: <20200608121723.7a042105@hermes.lan>
On Tue, Jun 9, 2020 at 12:47 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> On Mon, 8 Jun 2020 17:46:40 +0100
> Bruce Richardson <bruce.richardson@intel.com> wrote:
>
> > Rather than continuing to recommend an 80-char line limit, let's take a hint
> > from the Linux kernel[1] and aim for an 100-char recommended limit instead.
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bdc48fa11e46f867ea4d75fa59ee87a7f48be144
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> > devtools/checkpatches.sh | 2 +-
> > doc/guides/contributing/coding_style.rst | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/devtools/checkpatches.sh b/devtools/checkpatches.sh
> > index 158087f1c..4970ed830 100755
> > --- a/devtools/checkpatches.sh
> > +++ b/devtools/checkpatches.sh
> > @@ -15,7 +15,7 @@ VALIDATE_NEW_API=$(dirname $(readlink -f $0))/check-symbol-change.sh
> > # Codespell can also be enabled by setting DPDK_CHECKPATCH_CODESPELL to a valid path
> > # to a dictionary.txt file if dictionary.txt is not in the default location.
> > codespell=${DPDK_CHECKPATCH_CODESPELL:-enable}
> > -length=${DPDK_CHECKPATCH_LINE_LENGTH:-80}
> > +length=${DPDK_CHECKPATCH_LINE_LENGTH:-100}
> >
> > # override default Linux options
> > options="--no-tree"
> > diff --git a/doc/guides/contributing/coding_style.rst b/doc/guides/contributing/coding_style.rst
> > index 4efde93f6..1db3a7bbe 100644
> > --- a/doc/guides/contributing/coding_style.rst
> > +++ b/doc/guides/contributing/coding_style.rst
> > @@ -21,7 +21,7 @@ The rules and guidelines given in this document cannot cover every situation, so
> > * In the case of creating new files, the style should be consistent within each file in a given directory or module.
> > * The primary reason for coding standards is to increase code readability and comprehensibility, therefore always use whatever option will make the code easiest to read.
> >
> > -Line length is recommended to be not more than 80 characters, including comments.
> > +Line length is recommended to be not more than 100 characters, including comments.
> > [Tab stop size should be assumed to be 8-characters wide].
> >
> > .. note::
>
> I would even support going to 120 characters.
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Jerin Jacob <jerinj@marvell.com>
next prev parent reply other threads:[~2020-06-09 4:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 16:46 Bruce Richardson
2020-06-08 19:17 ` Stephen Hemminger
2020-06-09 4:42 ` Jerin Jacob [this message]
2020-06-09 9:29 ` Bruce Richardson
2020-06-09 10:00 ` Ananyev, Konstantin
2020-06-09 13:40 ` Andrew Rybchenko
2020-06-09 13:57 ` Bruce Richardson
2020-06-10 5:22 ` Jerin Jacob
2020-06-10 8:27 ` Andrew Rybchenko
2020-06-10 8:47 ` Jerin Jacob
2020-06-10 9:28 ` Andrew Rybchenko
2020-06-10 9:59 ` Bruce Richardson
2020-08-07 0:29 ` Thomas Monjalon
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=CALBAE1NufwR+FuzJNFV5G6dvaNiCGHW-r12CqxyKHoqwtW7CpA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).