From: corbet@lwn.net (Jonathan Corbet)
To: linux-security-module@vger.kernel.org
Subject: converting Documentation/security/* to .rst
Date: Mon, 1 May 2017 09:11:59 -0600 [thread overview]
Message-ID: <20170501091159.63218239@lwn.net> (raw)
In-Reply-To: <CAGXu5j+YuXd70ZCNBJRfQNXwMqSPgVaqEyaq_yXkbgje3-gdVg@mail.gmail.com>
On Fri, 28 Apr 2017 13:24:36 -0700
Kees Cook <keescook@google.com> wrote:
> I was curious if the conversion of security/ (and prctl/ which only
> has two files that should probably both be moved to security/) was
> already on someone's TODO list? I'd love to get these done (I refer
> people regularly to seccomp_filter.txt and self-protection.txt), but I
> didn't want to duplicate any efforts.
If anybody is working in that area, they've not told me about it.
> I read about various tools to help with auto-converting files to kind
> of help speed up the process, but I couldn't find what seemed a
> canonical answer to what to use as a helper. Is there one? (Perhaps
> this was only for DocBook?)
The tools, such as they are, are for the conversion of DocBook template
files. Most of the kernel's .txt files are already in something quite
close to RST already, so the conversion is trivial.
The real question would be one of organization. Most of the security
stuff looks like it properly belongs in the admin guide, but that's not
universally the case.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-01 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 20:24 converting Documentation/security/* to .rst Kees Cook
2017-05-01 15:11 ` Jonathan Corbet [this message]
2017-05-01 16:31 ` Kees Cook
2017-05-03 21:42 ` Jonathan Corbet
2017-05-05 21:54 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170501091159.63218239@lwn.net \
--to=corbet@lwn.net \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).