Git development
 help / color / mirror / Atom feed
From: Howard Johnson <hwj@BridgeportContractor.com>
To: git@vger.kernel.org
Subject: link broken on git man page
Date: Sun, 16 Oct 2016 13:42:12 -0700	[thread overview]
Message-ID: <db083f89-b502-fe61-ce62-e7c4701f8764@BridgeportContractor.com> (raw)

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.


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



             reply	other threads:[~2016-10-16 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 20:42 Howard Johnson [this message]
2016-10-16 21:04 ` link broken on git man page Pranit Bauva
2016-10-16 21:17 ` Jeff King

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=db083f89-b502-fe61-ce62-e7c4701f8764@BridgeportContractor.com \
    --to=hwj@bridgeportcontractor.com \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox