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  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]
Date:	Sun, 21 Dec 2014 09:09:52 -0800
From:	Joe Perches <>
To:	Alexander Holler <>
Cc:	Jonathan Corbet <>,,
Subject: Re: [RFC PATCH] CodingStyle: remove what nowadays might be
 considered polemic

On Sun, 2014-12-21 at 11:23 +0100, Alexander Holler wrote:
> Am 19.12.2014 um 14:36 schrieb Alexander Holler:
> > In times where things like checkpatch do exist and are mandated to be used,
> > it would be easy to warn if too many levels of indentation are used (e.g.
> > by counting leading tabs).

checkpatch already does that looking for 6+ leading
tabs then any statement that increases indentation.

> I've heared that wrong argument that a maximum line length 
> of 80 chars helps in regard to keep the levels of intendation low once 
> too often.

I believe that argument correct.

helps is not a mandate.

The idea is that code that start far from the left
(for some definition of far) is a signal that code
could be refactored into more discrete chunks.

Without a limit to line length, more code would
likely not have been as disaggregated as today.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists