lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9pf7i6u4UXS0eJ_YN8q5K2wtUx0iAS+rb4b=7FiWJNwKQ@mail.gmail.com>
Date:   Mon, 1 Jun 2020 05:18:36 -0600
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Joe Perches <joe@...ches.com>
Cc:     Netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>
Subject: Re: [PATCH net-next 1/1] wireguard: reformat to 100 column lines

On Mon, Jun 1, 2020 at 5:12 AM Joe Perches <joe@...ches.com> wrote:
> Newspaper columns are pretty narrow for a reason.
>
> Please remember that left to right scanning of text, especially for
> comments, is not particularly improved by longer lines.

I agree that extra long lines make reading text impossible -- 500 is
madness, for example -- but 100 columns is a marked improvement over
80 in reading quickly for me, where I can take in more text on one
glance. I regularly will reformat long emails in vim with gq, and I'm
not the only one who does that; it was a nice suggestion made to me
years ago.

Either way, I would prefer not to bikeshed these minutia. If you want
to impose a different column limit for comments than for the rest of
the code, I suggest you bring that up in the original thread where
Linus was discussing this stuff and codify it there as part of the
style guide. Please don't derail this patch before net-next closes
tomorrow; that will make things a larger headache than necessary.

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ