From: Stephan Mueller <stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
To: Michael Kerrisk
<michael.kerrisk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Handling of updates to kernel Documentation/ tree
Date: Mon, 09 Mar 2015 15:17:58 +0100 [thread overview]
Message-ID: <3421611.4D45Q2BAys@tauon> (raw)
Hi Michael,
how shall an update to the Documentation/ tree be handled in man pages
that contain a pointer to these documents?
Specifically, socket(2) contains a reference to
Documentation/crypto/crypto-API-userspace.txt. With the patch [1] the
document is gone and its contents is moved into a DocBook.
Shall the kernel DocBook website [2] be referenced? If so, when is it
appropriate to add the patch (note, the change is expected to be
propagated to Linus' tree in 4.1-rc1).
[1]
https://git.kernel.org/cgit/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=dbe5fe7e1b3b3632bef2c09964a5f5505de4d744
[2] https://www.kernel.org/doc/htmldocs/crypto-API/index.html
Ciao
Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-03-09 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 14:17 Stephan Mueller [this message]
2015-03-09 15:07 ` Handling of updates to kernel Documentation/ tree Christoph Hellwig
[not found] ` <20150309150739.GA6131-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-03-09 16:03 ` Michael Kerrisk (man-pages)
[not found] ` <54FDC468.40503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-09 16:05 ` Christoph Hellwig
[not found] ` <20150309160520.GA28067-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-03-10 5:56 ` Michael Kerrisk (man-pages)
2015-03-09 16:16 ` Stephan Mueller
2015-03-09 17:40 ` Mike Frysinger
2015-03-10 5:56 ` Michael Kerrisk (man-pages)
2015-03-10 14:11 ` Christoph Hellwig
[not found] ` <20150310141104.GA17228-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-03-12 9:56 ` Stephan Mueller
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=3421611.4D45Q2BAys@tauon \
--to=stephan.mueller-fwyzokdejagavxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.kerrisk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).