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: <Pine.LNX.4.64.0912181137140.23738@hs20-bc2-1.build.redhat.com>
Date:	Fri, 18 Dec 2009 11:43:23 -0500 (EST)
From:	Mikulas Patocka <mpatocka@...hat.com>
To:	kevin granade <kevin.granade@...il.com>
cc:	Krzysztof Halasa <khc@...waw.pl>, Valdis.Kletnieks@...edu,
	Paul Mundt <lethal@...ux-sh.org>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alasdair G Kergon <agk@...hat.com>, dm-devel@...hat.com
Subject: Re: [PATCH] Drop 80-character limit in checkpatch.pl

> Note: I'm not specifically arguing for keeping the 80-column rule, the
> project I work on uses 100 columns, and that's quite workable, but I
> haven't had any problem working with 80 columns as a limit either.  I
> do however think that just removing the limit without replacing it
> with something better is a bad idea.
> 
> -Kevin Granade

But think what happens when someone views that 100-char code on 80-char 
terminal (or for example 94-char, that I used for some times too) --- 
every second line will be wasted with just 20 characters on the left. On 
the other hand, if you have unlimited line length, it will look better on 
80-char terminal.

Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ