linux-kernel - Re: [PATCH] docs: rewrite admin-guide/sysctl/abi.rst

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] [day] [month] [year] [list]

Date:   Thu, 17 Sep 2020 09:03:32 +0200
From:   Stephen Kitt <steve@....org>
To:     Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: rewrite admin-guide/sysctl/abi.rst

On Wed, 16 Sep 2020 12:43:10 -0600, Jonathan Corbet <corbet@....net> wrote:
> On Fri, 11 Sep 2020 21:01:52 +0200
> Stephen Kitt <steve@....org> wrote:
> > Following the structure used in sysctl/kernel.rst, this updates
> > abi.rst to use ReStructured Text more fully and updates the entries to
> > match current kernels:
> > 
> >   * the list of files is now the table of contents;
> >   * links are used to point to other documentation and other sections;
> >   * all the existing entries are no longer present, so this removes
> >     them;
> >   * document vsyscall32.
> > 
> > Mentions of the kernel version are dropped. Since the document is
> > entirely rewritten, I've replaced the copyright statement.
> > 
> > Signed-off-by: Stephen Kitt <steve@....org>  
> 
> Replacing a copyright makes me a little nervous, but I guess that is OK
> here since everything else is replaced too.

I hesitated too, but after checking carefully that the original contents were
all gone, decided it sort of made sense... I could just drop that line too,
I’m not sure there’s much point in documentation that’s supposed to be
collectively maintained (and authorship is determined by the commits anyway).

> Could I trouble you, though, for a version that adds an SPDX line at the
> top while you're at it?

No problem, v2 incoming.

While I’m at it, might I ask if it would be possible to carry
https://lkml.org/lkml/2020/8/12/181 (sort-of-re-submitted in
https://lkml.org/lkml/2020/9/11/1079) in the docs tree? It fixes a docs
commit...

Regards,

Stephen

Content of type "application/pgp-signature" skipped