linux-kernel - Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq

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: <28421.1208181120@vena.lwn.net>
Date:	Mon, 14 Apr 2008 07:52:00 -0600
From:	corbet@....net (Jonathan Corbet)
To:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>
CC:	Al Viro <viro@...IV.linux.org.uk>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: [PATCH 1/1] Fix typos in Documentation/filesystems/seq_file.txt 

Dmitri Vorobiev <dmitri.vorobiev@...il.com> wrote:

> Offhand, it seems that the double spacing convention is being currently used
> in a more or less consistent manner throughout Linux docs. It also seems to
> me that this can be made a requirement and documented somewhere.

Double spacing is my preference, and I appreciate your sending a new
patch which doesn't take that out.

But *please* let's not try to make "requirements" along those lines.  If
somebody's going to go to the trouble to write some documentation, I
don't think we really want people bouncing it back to them with 100
"single space after period" errors from checkpatch.pl...

Thanks,

jon
--
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/