From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>
Cc: "Thomas Ackermann" <th.acker@arcor.de>,
"W. Trevor King" <wking@tremily.us>,
"David Aguilar" <davvid@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Kevin Bracey" <kevin@bracey.fi>,
"Ondrej Bílka" <neleai@seznam.cz>, "Phil Hord" <hordp@cisco.com>,
"Sebastian Schuberth" <sschuberth@gmail.com>,
"Øystein Walle" <oystwa@gmail.com>
Subject: [PATCH] provide a Git user-manual man page
Date: Sat, 15 Feb 2014 13:51:38 +0000 [thread overview]
Message-ID: <1392472299-3780-1-git-send-email-philipoakley@iee.org> (raw)
This is a resend of my original patch ($gman/240486), which disappeared
without comment. I've cc'd those who have touched the User-Manual in
the last year for comment on the provision of this access mechanism.
The Git User Manual is formatted as a doc book, rather than as
a man page so isn't directly accessible via the usual 'git help
<guide>' command.
This patch provides a simple man page with onward links to the true
User-Manual.
The man page is based directly on a very cut down version of the git(1)
page.
This patch is based on 1.9.0 master.
Philip Oakley (1):
Provide a 'git help user-manual' route to the docbook
Documentation/Makefile | 1 +
Documentation/gituser-manual.txt | 34 ++++++++++++++++++++++++++++++++++
builtin/help.c | 1 +
3 files changed, 36 insertions(+)
create mode 100644 Documentation/gituser-manual.txt
--
1.8.3.msysgit.0
next reply other threads:[~2014-02-15 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 13:51 Philip Oakley [this message]
2014-02-15 13:51 ` [PATCH] Provide a 'git help user-manual' route to the docbook Philip Oakley
2014-02-18 20:14 ` Junio C Hamano
2014-02-18 22:39 ` Philip Oakley
-- strict thread matches above, loose matches on Subject: below --
2014-01-15 23:10 [PATCH] provide a Git user-manual man page Philip Oakley
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=1392472299-3780-1-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hordp@cisco.com \
--cc=kevin@bracey.fi \
--cc=neleai@seznam.cz \
--cc=oystwa@gmail.com \
--cc=sschuberth@gmail.com \
--cc=th.acker@arcor.de \
--cc=wking@tremily.us \
/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).