linux-kernel - Re: [PATCH 00/32] Create an User's manual and improve development-process book

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 18 Oct 2016 17:25:42 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc:     Jani Nikula <jani.nikula@...ux.intel.com>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/32] Create an User's manual and improve
 development-process book

On Tue, 18 Oct 2016 08:20:18 -0200
Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:

> > While at it, how about unifying some of the FilenamesInCamelCase,
> > filenames-with-hyphens, and filenames_with_underscores too...? To at
> > least move things towards just one of them within one directory.  
> 
> Sure, let's do it. I would just keep README as README.rst , as people
> are more used to see readme files on upercases.
> 
> For the rest, what's your preference?
> 
> 	- FooBar.rst
> 	- foo_bar.rst
> 	- foo-bar.rst
> 
> My personal preference is for "foo-bar".

I guess that would be mine too.  CamelCase is not generally all that
popular in kernel space.  On one hand, I worry about further renaming
files that we're already moving; on the other, if we're going to do it, I
guess this would be the time, when people will have to look for them
anyway...

jon