linux-man.vger.kernel.org archive mirror
 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: Thu, 12 Mar 2015 10:56:07 +0100	[thread overview]
Message-ID: <1506795.aItdcJcpob@tauon> (raw)
In-Reply-To: <20150310141104.GA17228-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

Am Dienstag, 10. März 2015, 07:11:04 schrieb Christoph Hellwig:

Hi Christoph,

>On Mon, Mar 09, 2015 at 01:40:57PM -0400, Mike Frysinger wrote:
>> > 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.
>
>The content really should not change that much for public APIs.
>
>> i think having the man pages refer to the public docbook kernel.org
>> pages should be fine.
>
>Pointing to kernel.org posted html renderings sounds perfectly fine to
>me.  The reference to files inside a kernel source tree is what I
>object to.
>--
>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

If this is the consensus, then I will wait with a patch to the man page 
until the code is merged into Linus' tree and the DocBook at kernel.org 
is updated.

The patch will then refer to the precise kernel.org web page.


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-12  9:56 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
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 [this message]

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=1506795.aItdcJcpob@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;
as well as URLs for NNTP newsgroup(s).