From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 00/15] Updates of in-kernel documentation pointers
Date: Mon, 11 Sep 2017 04:47:47 -0700 [thread overview]
Message-ID: <20170911114747.GA3463@infradead.org> (raw)
In-Reply-To: <20170911030347.GA24854-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
On Mon, Sep 11, 2017 at 05:03:47AM +0200, Eugene Syromyatnikov wrote:
> Hello.
>
> I've noticed that some of Linux kernel in-tree documentation pointers
> are no longer valid and decided to check the validity for the rest of
> them with some one-liner. As it turned out, there are quite a few of
> them, in part due to latest ReST conversion effort. This patch set aims
> at amending documentation pointers that are no longer valid with the
> information about current location. I'm not quite sure about
> wording/formatting, and do not guarantee that I haven't miss anything,
> so I hope that this could be at least useful as a starting point.
Do these pointers even have a place in man pages? I'd much rather
have anything that matters added to the man page instead.
--
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:[~2017-09-11 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 3:03 [PATCH 00/15] Updates of in-kernel documentation pointers Eugene Syromyatnikov
[not found] ` <20170911030347.GA24854-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2017-09-11 11:47 ` Christoph Hellwig [this message]
[not found] ` <20170911114747.GA3463-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-09-11 11:56 ` Eugene Syromyatnikov
2017-09-11 13:54 ` Michael Kerrisk (man-opages)
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=20170911114747.GA3463@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=evgsyr-Re5JQEeQqe8AvxtiuMwx3w@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