linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Manual Pages <man-pages@man7.org>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@redhat.com>
Subject: About http://man7.org/linux/man-pages/man8/xfs_repair.8.html
Date: Wed, 10 Apr 2019 08:01:22 -0700	[thread overview]
Message-ID: <20190410150122.GA1019523@magnolia> (raw)

Hi,

I was browsing man7.org looking for manual pages and came across this:

http://man7.org/linux/man-pages/man8/xfs_repair.8.html

Hm, that's cool that it pulls in xfsprogs manpages now. :)

Unfortunately, I got to the bottom and saw:

   "Information about the project can be found at ⟨http://xfs.org/⟩. If
   you have a bug report for this manual page, see
   ⟨http://oss.sgi.com/bugzilla/buglist.cgi?product=XFS⟩.  This page was
   obtained from the project's upstream Git repository
   ⟨git://oss.sgi.com/xfs/cmds/xfsprogs⟩ on 2019-03-06.  (At that time,
   the date of the most recent commit that was found in the repository
   was 2019-02-22.)"

The last two URLs here are incorrect.  Linux XFS no longer uses any SGI
servers, I think oss.sgi.com has been dead for 18 months, and xfs.org .
In any case, bug reports should go to [1] and the upstream git repo is
[2].  Could you please update whatever's generating man7.org?

Thanks,

--D

[1] mailto:linux-xfs@vger.kernel.org
[2] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/

             reply	other threads:[~2019-04-10 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 15:01 Darrick J. Wong [this message]
2019-04-12 14:30 ` About http://man7.org/linux/man-pages/man8/xfs_repair.8.html 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=20190410150122.GA1019523@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=man-pages@man7.org \
    --cc=mtk.manpages@gmail.com \
    --cc=sandeen@redhat.com \
    /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).