From: Joe Perches <joe@perches.com>
To: David Rientjes <rientjes@google.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Hugh Dickins <hughd@google.com>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: Use octal not symbolic permissions
Date: Mon, 26 Mar 2018 16:05:14 -0700 [thread overview]
Message-ID: <1522105514.12357.38.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1803261535460.93873@chino.kir.corp.google.com>
On Mon, 2018-03-26 at 15:36 -0700, David Rientjes wrote:
> extending some of these lines to be >80 characters also improves
> the readability imo.
Right.
I have no personal objection to very occasionally using
line lengths < ~100 chars instead of 80.
AFAIK: neither does Linus.
https://lkml.org/lkml/2016/12/15/749
Beyond that, I believe it's too much left-right eyeball
movement for quick and easy reading comprehension.
next prev parent reply other threads:[~2018-03-26 23:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 22:22 Joe Perches
2018-03-26 22:36 ` David Rientjes
2018-03-26 23:05 ` Joe Perches [this message]
2018-03-26 22:41 ` Andrew Morton
2018-03-26 22:50 ` Joe Perches
2018-03-28 13:06 ` Michal Hocko
2018-03-28 15:44 ` Joe Perches
2018-03-28 19:07 ` Michal Hocko
2018-03-28 19:26 ` Joe Perches
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=1522105514.12357.38.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=ddstreet@ieee.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sjenning@redhat.com \
/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