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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20161019072717.661c45fc@vento.lan>
Date:   Wed, 19 Oct 2016 07:27:17 -0200
From:   Mauro Carvalho Chehab <mchehab@...pensource.com>
To:     Jonathan Corbet <corbet@....net>
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

Em Tue, 18 Oct 2016 17:25:42 -0600
Jonathan Corbet <corbet@....net> escreveu:

> 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...

It was also somewhat painful to do the renames, but IMHO, it is for
a greater good. Anyway, the version 2 of this series, submitted
yesterday, is doing the renames to foo-bar.rst. I merged all renames
on a single patch, per book. So, if we still need to change something,
there will be no need on touching on the ReST conversion patches.

There were a few issues that I noticed on the version 2, but I
wait for a couple of days before sending the final version, in order
to give people more time to review.

Regards,
Mauro