All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Joe Perches <joe@perches.com>
Cc: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>,
	netdev@vger.kernel.org
Subject: Re: [PATCH RFC iproute2-next v4] tc: add support for action act_ctinfo
Date: Wed, 5 Jun 2019 11:54:36 -0700	[thread overview]
Message-ID: <20190605115436.3092dd50@hermes.lan> (raw)
In-Reply-To: <95fa3d641e5df79b7e69ff377593c4273e812bb6.camel@perches.com>

On Wed, 05 Jun 2019 11:23:59 -0700
Joe Perches <joe@perches.com> wrote:

> Strict 80 column limits with long identifiers are just silly.
> 
> I don't know how strictly enforced the iproute2 80 column limit
> actually is, but I suggest ignoring that limit where appropriate.


Not strictly enforced, but long identifiers are discouraged.
Overly deep nesting which is the main cause of long lines
is also discouraged.

      reply	other threads:[~2019-06-05 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31  8:10 [PATCH RFC iproute2-next v2] tc: add support for act ctinfo ldir.kdb
2019-06-02  7:33 ` Kevin 'ldir' Darbyshire-Bryant
2019-06-02 18:50 ` [PATCH RFC iproute2-next v3] tc: add support for action act_ctinfo Kevin Darbyshire-Bryant
2019-06-02 20:39   ` Toke Høiland-Jørgensen
2019-06-02 21:55     ` Kevin 'ldir' Darbyshire-Bryant
2019-06-03  9:15       ` Toke Høiland-Jørgensen
2019-06-03 13:50   ` [PATCH RFC iproute2-next v4] " Kevin Darbyshire-Bryant
2019-06-03 20:14     ` Toke Høiland-Jørgensen
2019-06-05 18:23     ` Joe Perches
2019-06-05 18:54       ` Stephen Hemminger [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=20190605115436.3092dd50@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=joe@perches.com \
    --cc=ldir@darbyshire-bryant.me.uk \
    --cc=netdev@vger.kernel.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.