git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Daniel Campbell <zlg@gentoo.org>
To: git@vger.kernel.org
Subject: `man 1 git`: Invalid link to online documentation
Date: Sun, 5 Jun 2016 20:59:00 -0700	[thread overview]
Message-ID: <ed8f000f-b8a2-ca92-e0f2-e26ff9928bbe@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1220 bytes --]

In `man 1 git`, the Description section outlines an address to
pre-generated documentation [0]. That link returns a 404 error. Playing
around, I found the repository at [1] and found that it hasn't been
updated since August 2015. Given that 2.8.3 is more recent than that, it
seems like this is something that should be updated (if the
pre-generated docs still exist somewhere) or removed altogether.

Also worth considering is Google Code was shut down earlier this year.
While archives exist, it can't be relied upon for future use. The
closest approximation I could find that was up to date is [2], though
[3] is a repository that's even fresher than 2.8.3.

Since I'm not familiar with Git development I figured it was wiser to
let you know instead of making a decision on what to do and patching.

I know this is minor but I figured it was overlooked. Thanks for reading.

0: http://git-htmldocs.googlecode.com/git/git.html
1: https://code.google.com/archive/p/git-htmldocs/
2: https://git-scm.com/docs
3: https://github.com/gitster/git-htmldocs
-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-06-06  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  3:59 Daniel Campbell [this message]
2016-06-06 23:19 ` `man 1 git`: Invalid link to online documentation Jeff King
2016-06-06 23:25   ` Jeff King
2016-06-08 12:43     ` Michael J Gruber

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed8f000f-b8a2-ca92-e0f2-e26ff9928bbe@gentoo.org \
    --to=zlg@gentoo.org \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).