From: Jakub Narebski <jnareb@gmail.com>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Is there a pdf git manual?
Date: Mon, 07 Nov 2011 10:53:34 -0800 (PST) [thread overview]
Message-ID: <m3obwn3gtz.fsf@localhost.localdomain> (raw)
In-Reply-To: <CABrM6wkzV58WLnHkZ88y=MQVWjD8dwYMtG9HTto8t8QXBEW-hA@mail.gmail.com>
Peng Yu <pengyu.ut@gmail.com> writes:
> Hi,
>
> http://schacon.github.com/git/user-manual.html
>
> The manual is in html. I'm not able to find a pdf version. Running
> make in git/Documentation doesn't generate a pdf document
> automatically. Could anybody generated the pdf document and post it to
> the git project website? Thanks!
"make pdf" would generate PDF version of (some of) documentation.
--
Jakub Narębski
next prev parent reply other threads:[~2011-11-07 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 17:24 Is there a pdf git manual? Peng Yu
2011-11-07 18:29 ` Tony Godshall
2011-11-07 18:53 ` Jakub Narebski [this message]
2011-11-07 19:07 ` Peng Yu
2011-11-07 23:17 ` Jakub Narebski
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=m3obwn3gtz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=pengyu.ut@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).