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: <87pomyvtac.fsf@intel.com>
Date:   Tue, 18 Oct 2016 13:35:39 +0300
From:   Jani Nikula <jani.nikula@...ux.intel.com>
To:     Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc:     Jonathan Corbet <corbet@....net>,
        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, Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:
> Em Tue, 18 Oct 2016 13:01:01 +0300
> Jani Nikula <jani.nikula@...ux.intel.com> escreveu:
>
>> On Tue, 18 Oct 2016, Jonathan Corbet <corbet@....net> wrote:
>> > So I raised this topic in talks at both Kernel Recipes and LinuxCon
>> > Europe, and nobody threw things at me.  I have come to suspect that I'm
>> > worrying a little too much about it; maybe we should go ahead and move
>> > the documents and see who screams.  
>> 
>> 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.

Right, I guess I'd keep the top level files as-is, and just do this
within Documentation.

> For the rest, what's your preference?
>
> 	- FooBar.rst
> 	- foo_bar.rst
> 	- foo-bar.rst
>
> My personal preference is for "foo-bar".

Same here, but I don't mind so much *which* one it is as long as at
least each directory has consistent naming.

> Thanks! Life would be very boring if everybody would have the same
> opinion :) So, feel free to disagree with me. Your views are very 
> welcome, even when differs from my own :)

Thanks, good to check we're on the same page here and not
antagonizing. :)


BR,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center