git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Neal Kreitzinger <nkreitzinger@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git info pages
Date: Thu, 21 Jun 2012 02:26:24 -0400	[thread overview]
Message-ID: <20120621062624.GC19485@sigill.intra.peff.net> (raw)
In-Reply-To: <jrtlok$n11$1@dough.gmane.org>

On Wed, Jun 20, 2012 at 06:18:45PM -0500, Neal Kreitzinger wrote:

> Are there git 'info' pages or some other form of more extensive
> documentation somewhere that I can look at to get more information
> than what the git 'man' pages have?

There are info pages, but they contain the same text as the manpages.
Look in git.git's Documentation/ subtree. There are a few things which
don't make it to manpage format (like user-manual.txt, technical/, and
howto/) but the manpages are generally the most up-to-date and complete
documentation there is.

What are you looking for in particular?

You might also try the free Pro Git if you're looking for more
discussion:

  http://git-scm.com/book

-Peff

      reply	other threads:[~2012-06-21  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 23:18 git info pages Neal Kreitzinger
2012-06-21  6:26 ` Jeff King [this message]

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=20120621062624.GC19485@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=nkreitzinger@gmail.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).