From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, stephen@networkplumber.org, jerinj@marvell.com,
arybchenko@solarflare.com, david.marchand@redhat.com,
ferruh.yigit@intel.com, olivier.matz@6wind.com,
akhil.goyal@nxp.com
Subject: Re: [dpdk-dev] [PATCH RFC] devtools: increase default line length to 100
Date: Fri, 07 Aug 2020 02:29:21 +0200 [thread overview]
Message-ID: <3450700.74BcBIW3jB@thomas> (raw)
In-Reply-To: <20200608164640.189755-1-bruce.richardson@intel.com>
08/06/2020 18:46, Bruce Richardson:
> 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>
> ---
> -length=${DPDK_CHECKPATCH_LINE_LENGTH:-80}
> +length=${DPDK_CHECKPATCH_LINE_LENGTH:-100}
This is my personnal settings for years.
[...]
> -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.
I think lines of 80 characters are reasonnable,
but I would not reject a patch because few lines are between 80 and 100.
I would reword the doc to reflect that flexibility:
"
Line length is recommended to be not more than 80 characters, including comments.
The hard limit is 100 characters.
"
prev parent reply other threads:[~2020-08-07 0:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 16:46 [dpdk-dev] [PATCH RFC] devtools: increase default line length to 100 Bruce Richardson
2020-06-08 19:17 ` Stephen Hemminger
2020-06-09 4:42 ` Jerin Jacob
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 [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=3450700.74BcBIW3jB@thomas \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=olivier.matz@6wind.com \
--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 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.