linux-kernel - Re: [PATCH v3 05/21] Documentation/applying-patches.txt: convert it to ReST markup

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: <20160916172536.5952bf4a@vento.lan>
Date:   Fri, 16 Sep 2016 17:25:36 -0300
From:   Mauro Carvalho Chehab <mchehab@...pensource.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...radead.org>,
        Markus Heiser <markus.heiser@...marit.de>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 05/21] Documentation/applying-patches.txt: convert it
 to ReST markup

Em Fri, 16 Sep 2016 11:10:26 -0600
Jonathan Corbet <corbet@....net> escreveu:

> On Wed, 14 Sep 2016 08:06:34 -0300
> Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:
> 
> > - use the correct markup to identify each section;
> > 
> > - Add some blank lines for Sphinx to properly interpret
> >   the markups;
> > 
> > - Remove a blank space on some paragraphs;
> > 
> > - Fix the verbatim and bold markups;
> > 
> > - Cleanup the remaining errors to make Sphinx happy.  
> 
> So I certainly don't have a problem with the changes made to this file, but
> there is some discomfort at a higher level:
> 
> > +Last update:
> > +	2006-01-05  
> 
> I have to wonder what the value of a document saying how to FTP the patch
> and move up to 2.6.13 is in 2016.

As you're commenting my first patch series, I suspect you didn't
see the second one yet ;)
Its subject is:
	[PATCH 00/17] Improve documentation for the development-process

There, I read all files that were moved to the development-process
dir, and updated some things. I didn't read yet the files that were
already there, but, as they're newer, I suspect they should be
more synchronized with the status quo.

In the case of this file, I updated it to point to  4.x, removed some
legacy stuff, like the -git tarballs and updated the parts that
mention the -mm kernels, adding a notice about linux-next.
The patch is at:
	https://patchwork.kernel.org/patch/9332673/

> 
> Who knows, there might still be value in a discussion of using the patch
> tool.

Well, it teaches how to use the "patch" tool, with can be useful
for newbies. It also explains how the incremental and non-incremental
Kernel patches work. So, I guess it is still useful.

> But I think we should seriously consider making a "historical"
> section for documents that are nearing or past their expiration dates.


> 
> jon



Thanks,
Mauro