From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] editorconfig: bump line length to 100
Date: Wed, 20 Oct 2021 16:57:41 +0300 [thread overview]
Message-ID: <59c1feb2-72c1-f1bd-a55f-dcec95751659@oktetlabs.ru> (raw)
In-Reply-To: <20211020134840.2421686-1-bruce.richardson@intel.com>
On 10/20/21 4:48 PM, Bruce Richardson wrote:
> Since we allow line lengths of up to 100, adjust the editorconfig to use
> that value, to save editors (such as vim) from automatically wrapping
> lines at 80 characters when typing.
DPDK_CHECKPATCH_LINE_LENGTH default is 80 in
devtools/checkpatches.sh
>
> Since python checkers all seem to expect 79 character lines max, add for
> python only a 79-char max line length.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> .editorconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/.editorconfig b/.editorconfig
> index 5101630c8c..ab41c95085 100644
> --- a/.editorconfig
> +++ b/.editorconfig
> @@ -11,11 +11,12 @@ trim_trailing_whitespace = true
> charset = utf-8
> indent_style = tab
> tab_width = 8
> -max_line_length = 80
> +max_line_length = 100
>
> [*.py]
> indent_style = space
> indent_size = 4
> +max_line_length = 79
>
> [meson.build]
> indent_style = space
>
next prev parent reply other threads:[~2021-10-20 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 13:48 Bruce Richardson
2021-10-20 13:57 ` Andrew Rybchenko [this message]
2021-10-20 14:11 ` Bruce Richardson
2021-10-20 14:14 ` Bruce Richardson
2021-10-20 14:26 ` [dpdk-dev] [PATCH v2] devtools: clarify that lines up to 100 characters are ok Bruce Richardson
2021-10-20 14:28 ` Andrew Rybchenko
2021-10-22 0:11 ` Jerin Jacob
2021-11-25 10:51 ` Thomas Monjalon
2021-10-22 8:21 ` Xia, Chenbo
2021-10-26 0:30 ` fengchengwen
2021-10-28 13:14 ` Walsh, Conor
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=59c1feb2-72c1-f1bd-a55f-dcec95751659@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--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).