threads / discuss / 44309

link broken on git man page

Subject: link broken on git man page

## tl;dr

3 messages between Oct 16, 2016 and Oct 16, 2016.

replies: 2people: 3as markdown or json

Howard Johnson· Oct 16, 2016, 20:42 UTC · lore

This link below is broken in the man page.  (I'm on Debian Jessie).

GIT(1) Git Manual GIT(1)

NAME
        git - the stupid content tracker

SYNOPSIS
        git [--version] [--help] [-C <path>] [-c <name>=<value>]
            [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
            [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
            [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
            <command> [<args>]

DESCRIPTION
        Git is a fast, scalable, distributed revision control system with an
        unusually rich command set that provides both high-level 
operations and
        full access to internals.

        See gittutorial(7) to get started, then see Everyday Git[1] for a
        useful minimum set of commands. The Git User’s Manual[2] has a more
        in-depth introduction.

        After you mastered the basic concepts, you can come back to this 
page
        to learn what commands Git offers. You can learn more about 
individual
        Git commands with "git help command". gitcli(7) manual page 
gives you
        an overview of the command-line command syntax.

        Formatted and hyperlinked version of the latest Git 
documentation can
        be viewed at http://git-htmldocs.googlecode.com/git/git.html.

                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Pranit Bauva· Oct 16, 2016, 21:04 UTC · re: Howard Johnson · lore

Re: link broken on git man page

Hey Howard,

On Mon, Oct 17, 2016 at 2:12 AM, Howard Johnson <hwj@bridgeportcontractor.com> wrote:

Show 38 quoted lines

> This link below is broken in the man page.  (I'm on Debian Jessie).
>
>
> GIT(1)                            Git Manual
> GIT(1)
>
> NAME
>        git - the stupid content tracker
>
> SYNOPSIS
>        git [--version] [--help] [-C <path>] [-c <name>=<value>]
>            [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
>            [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
>            [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
>            <command> [<args>]
>
> DESCRIPTION
>        Git is a fast, scalable, distributed revision control system with an
>        unusually rich command set that provides both high-level operations
> and
>        full access to internals.
>
>        See gittutorial(7) to get started, then see Everyday Git[1] for a
>        useful minimum set of commands. The Git User’s Manual[2] has a more
>        in-depth introduction.
>
>        After you mastered the basic concepts, you can come back to this page
>        to learn what commands Git offers. You can learn more about
> individual
>        Git commands with "git help command". gitcli(7) manual page gives you
>        an overview of the command-line command syntax.
>
>        Formatted and hyperlinked version of the latest Git documentation can
>        be viewed at http://git-htmldocs.googlecode.com/git/git.html.
>
>
>                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>

It is fixed in the recent version 2.10.0 . The new link is https://git.github.io/htmldocs/git.html .

Regards, Pranit Bauva

Jeff King· Oct 16, 2016, 21:17 UTC · re: Howard Johnson · lore

Re: link broken on git man page

On Sun, Oct 16, 2016 at 01:42:12PM -0700, Howard Johnson wrote:

> This link below is broken in the man page.  (I'm on Debian Jessie).
> [...]
>        Formatted and hyperlinked version of the latest Git documentation can
>        be viewed at http://git-htmldocs.googlecode.com/git/git.html.

This is fixed already in f793582 (doc: git-htmldocs.googlecode.com is no more, 2016-06-22), which is in git v2.9.1. Debian testing/unstable are at v2.9.3, but Jessie is still on v2.1.4.

I don't know the policy for cherry-picking patches to Debian stable releases. I think only security fixes are done immediately, but "important" fixes get rolled into stable updates every few months. I don't know that this is "important", but it does point to information that grew stale outside of the release's control, and as a trivial documentation-only change, it shouldn't cause a regression.

+cc Jonathan, who works on git packaging for Debian.

-Peff