public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan Mueller <stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Michael Kerrisk
	<michael.kerrisk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Handling of updates to kernel Documentation/ tree
Date: Mon, 09 Mar 2015 17:16:37 +0100	[thread overview]
Message-ID: <43211791.W2j9vX2NNy@tauon> (raw)
In-Reply-To: <20150309150739.GA6131-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

Am Montag, 9. März 2015, 08:07:39 schrieb Christoph Hellwig:

Hi Christoph,

>On Mon, Mar 09, 2015 at 03:17:58PM +0100, Stephan Mueller wrote:
>> 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).
>
>Referencing a kernel Documentation file from a man page sounds like
>a bad idea to me.  Why can't we include a nroff-yfied version of the
>content in the man-pages repository?

You can see the compiled output at [1]. You see that the output is 
larger. Of course I can provide a patch of the output from make mandocs 
of that DocBook. I would think that this documentation is too large to 
be put into socket(2).

The only proposal I would have is to format the output into a separate 
man page for chapter 4.

[1] http://www.chronox.de/crypto-API/User.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

  parent reply	other threads:[~2015-03-09 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 14:17 Handling of updates to kernel Documentation/ tree Stephan Mueller
2015-03-09 15:07 ` 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 [this message]
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=43211791.W2j9vX2NNy@tauon \
    --to=stephan.mueller-fwyzokdejagavxtiumwx3w@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@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