All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Walsh, Conor" <conor.walsh@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] devtools: clarify that lines up to 100 characters are ok
Date: Thu, 28 Oct 2021 13:14:53 +0000	[thread overview]
Message-ID: <PH0PR11MB52076FFBEE4057F2ECFC0817FF869@PH0PR11MB5207.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211020142601.157649-1-bruce.richardson@intel.com>

> From: dev <dev-bounces@dpdk.org> On Behalf Of Bruce Richardson
> Sent: Wednesday 20 October 2021 15:26
> To: dev@dpdk.org
> Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>; Richardson,
> Bruce <bruce.richardson@intel.com>
> Subject: [dpdk-dev] [PATCH v2] devtools: clarify that lines up to 100
> characters are ok
> 
> Since we allow line lengths of up to 100, and the CI checkpatches job
> only check for that amount, the rest of our tooling and docs should
> reflect this reality. Therefore we can:
> 
> * adjust the editorconfig to use that value, to save editors (e.g. vim)
>   from automatically wrapping lines at 80 characters when typing.
>   [Since python checkers all seem to expect 79 character lines max, add
>   for python only a 79-char max line length.]
> 
> * change the default line length setting in checkpatches script to 100
>   so as it matches CI and pre-merge checks.
> 
> * update the docs to clarify that while 80 chars is recommended, up to
>   100 characters is acceptable.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---

I think it would be great to have clarity around this, since it seems to already be allowed.
Acked-by: Conor Walsh <conor.walsh@intel.com>

      parent reply	other threads:[~2021-10-28 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 13:48 [dpdk-dev] [PATCH] editorconfig: bump line length to 100 Bruce Richardson
2021-10-20 13:57 ` Andrew Rybchenko
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 [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=PH0PR11MB52076FFBEE4057F2ECFC0817FF869@PH0PR11MB5207.namprd11.prod.outlook.com \
    --to=conor.walsh@intel.com \
    --cc=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 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.