linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Piotr Dobrogost <p@lists-2014.dobrogost.net>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Lack of sshfs(1) man page
Date: Tue, 23 Dec 2014 16:38:41 +0100	[thread overview]
Message-ID: <54998C81.5090408@gmail.com> (raw)
In-Reply-To: <CAA6tFMtt4WO2SkSuMp=Yg9orSOGmD3ihnPH4LLDD30gTGzJK4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hello Piotr,

On 11/24/2014 03:20 PM, Piotr Dobrogost wrote:
> Hi!
> 
> I was looking for sshfs man page at
> http://man7.org/linux/man-pages/dir_section_1.html but it's not there.

I've added it to my scripts, so it'll go out with the next site refresh.
(See http://blog.man7.org/2013/05/adding-further-man-pages-to-html.html)

> At the same time there is such a page at
> http://linux.die.net/man/1/sshfs
> Am I missing something?

No. The set at man7.org is not as extensive as at linux.die.net...

> Also should I prefer man7.org/linux/man-pages/ man pages to
> http://linux.die.net/man/ ones?

It depends, and obviously I am biased. The pages rendered
at man7.org tend to be (*much*) more up to date, and the
COLOPHON tells you exactly where the page came from, and
when. That info is not available on most other sites that
provide HTML renderings, and the pages on some of those
sites are years out of date. As outlined in the blog post,
I am open to add projects to the rendered set, which currently
comprises around 100 projects.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2014-12-23 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:20 Lack of sshfs(1) man page Piotr Dobrogost
     [not found] ` <CAA6tFMtt4WO2SkSuMp=Yg9orSOGmD3ihnPH4LLDD30gTGzJK4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-23 15:38   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <54998C81.5090408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-12-24  0:07       ` Piotr Dobrogost
     [not found]         ` <CAA6tFMvS_+wjJ11T6CAgVGS4+nyGr6KiO-LVUWb-4Abf1nLU+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-24  8:21           ` 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=54998C81.5090408@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=p@lists-2014.dobrogost.net \
    /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).