From: Laurent Georget <laurent.georget-vbcOdlJ0SulGWvitb5QawA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch 1/2] adjtimex.2: remove nonexisting reference to adjtimex(8)
Date: Sat, 29 Nov 2014 11:22:38 +0100 [thread overview]
Message-ID: <54799E6E.2030600@supelec.fr> (raw)
In-Reply-To: <CAKgNAkhVxy9J4dQCGwEBNwWFj_vwj=xN0JNtBx=sECgP-GiusA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hello again,
Le 29/11/2014 10:17, Michael Kerrisk (man-pages) a écrit :
> Hello Laurent,
>
> On Fri, Nov 28, 2014 at 3:02 PM, Laurent Georget
> <laurent.georget-vbcOdlJ0SulGWvitb5QawA@public.gmane.org> wrote:
>> Hello,
>>
>> This is a patch I sent to mtk.manpages-Re5JQEeQqe9fmgfxC/sS/w@public.gmane.org It didn't make its way
>> to this mailing-list the first time. It's a trivial fix for an undefined
>> reference to adjtimex(8). Patch you received before (adjtimex.2: add
>> explanation about ADJ_TAI action) is patch 2/2 for adjtimex.2.
>
> This does not seem correct to me. Certainly on my Fedora system, there
> is an "adjtimex" package that installs adjtimex(8) page. So, this
> reference seems okay to me. Did I miss something?
>
Ok, indeed, my mistake. This package is not part of the core system on
my distribution so I found it surprising to have a link from a man2 page
to a nonexisting man8 page. But now that I give a closer look, the case
is the same for request_key.2 linking to request_key.8 for example so
I'm wrong.
What is the policy to include a link from section 2 to section 1 or 8? I
guess I'm misundestanding something here? Given the case of adjtimex(2)
linking to adjtimex(8) because there is an adjtimex package which
installs it, should we include a link in inotify_{init,add,...} to
inotifywait.1 for example? I've always thought that pages in section 1
(or 8) and 2 should just include a link to a general page in section 7
to remain generic enough through time.
Thanks,
Laurent
> Thanks,
>
> Michael
>
>
>> diff --git a/man2/adjtimex.2 b/man2/adjtimex.2
>> index eb3fda1..20a2f0b 100644
>> --- a/man2/adjtimex.2
>> +++ b/man2/adjtimex.2
>> @@ -24,6 +24,7 @@
>> .\" Modified 1997-01-31 by Eric S. Raymond <esr-4uCgticg2UFBDgjK7y7TUQ@public.gmane.org>
>> .\" Modified 1997-07-30 by Paul Slootman <paul-pqePwCal/LhZiXb3D+6dPA@public.gmane.org>
>> .\" Modified 2004-05-27 by Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> +.\" Modified 2014-11-28 by Laurent Georget <laurent.georget@supelec.fr>
>> .\"
>> .\" FIXME Document ADJ_TAI (added in Linux 2.6.26)
>> .\" commit 153b5d054ac2d98ea0d86504884326b6777f683d
>> @@ -163,5 +164,4 @@ method of adjusting the system clock.
>> .BR settimeofday (2),
>> .BR adjtime (3),
>> .BR capabilities (7),
>> -.BR time (7),
>> -.BR adjtimex (8)
>> +.BR time (7)
>> --
>> 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
>
>
>
--
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 prev parent reply other threads:[~2014-11-29 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 14:02 [patch 1/2] adjtimex.2: remove nonexisting reference to adjtimex(8) Laurent Georget
[not found] ` <54788059.6020209-vbcOdlJ0SulGWvitb5QawA@public.gmane.org>
2014-11-29 9:17 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkhVxy9J4dQCGwEBNwWFj_vwj=xN0JNtBx=sECgP-GiusA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-29 10:22 ` Laurent Georget [this message]
[not found] ` <54799E6E.2030600-vbcOdlJ0SulGWvitb5QawA@public.gmane.org>
2014-12-30 12:53 ` Michael Kerrisk (man-pages)
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=54799E6E.2030600@supelec.fr \
--to=laurent.georget-vbcodlj0sulgwvitb5qawa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-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).