All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Stephan Mueller
	<stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>,
	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, 9 Mar 2015 13:40:57 -0400	[thread overview]
Message-ID: <20150309174057.GC12857@vapier> (raw)
In-Reply-To: <20150309150739.GA6131-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

On 09 Mar 2015 08:07, Christoph Hellwig wrote:
> On Mon, Mar 09, 2015 at 03:17:58PM +0100, Stephan Mueller wrote:
> > 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?

isn't that way worse ?  now we have to keep the man pages git repo in sync with 
the kernel Documentation/ subtree.

i think having the man pages refer to the public docbook kernel.org pages should 
be fine.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-03-09 17:40 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
2015-03-09 17:40     ` Mike Frysinger [this message]
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=20150309174057.GC12857@vapier \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael.kerrisk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.