From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org, Drew Northup <drew.northup@maine.edu>
Cc: Jonathan Nieder <jrnieder@gmail.com>, Jakub Narebski <jnareb@gmail.com>
Subject: [PATCHv5 4/6] Documentation: Link to gitweb(1) and gitweb.conf(5) in other manpages
Date: Sat, 8 Oct 2011 20:32:01 +0200 [thread overview]
Message-ID: <1318098723-12813-5-git-send-email-jnareb@gmail.com> (raw)
In-Reply-To: <1318098723-12813-1-git-send-email-jnareb@gmail.com>
Add link to gitweb(1) in "SEE ALSO" section of git-instaweb(1) manpage,
and "Ancillary Commands" section of git(1) manpage (the latter by the
way of command-list.txt file).
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
This is new in this series.
BTW. why command-list.txt uses not only spaces to separate and align,
but also tabs, and mixtures of tabs and spaces???
Documentation/git-instaweb.txt | 4 ++++
command-list.txt | 1 +
2 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-instaweb.txt b/Documentation/git-instaweb.txt
index ea95c90..f3eef51 100644
--- a/Documentation/git-instaweb.txt
+++ b/Documentation/git-instaweb.txt
@@ -84,6 +84,10 @@ If the configuration variable 'instaweb.browser' is not set,
'web.browser' will be used instead if it is defined. See
linkgit:git-web{litdd}browse[1] for more information about this.
+SEE ALSO
+--------
+linkgit:gitweb[1]
+
GIT
---
Part of the linkgit:git[1] suite
diff --git a/command-list.txt b/command-list.txt
index 95bf18c..a36ee9b 100644
--- a/command-list.txt
+++ b/command-list.txt
@@ -130,5 +130,6 @@ git-upload-pack synchelpers
git-var plumbinginterrogators
git-verify-pack plumbinginterrogators
git-verify-tag ancillaryinterrogators
+gitweb ancillaryinterrogators
git-whatchanged ancillaryinterrogators
git-write-tree plumbingmanipulators
--
1.7.6
next prev parent reply other threads:[~2011-10-08 18:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 18:31 [PATCHv5/RFC 0/6] Moving gitweb documentation to manpages Jakub Narebski
2011-10-08 18:31 ` [PATCHv5/RFC 1/6] Documentation: Preparation for gitweb manpages Jakub Narebski
2011-10-10 18:53 ` Junio C Hamano
2011-10-10 21:52 ` Jakub Narebski
2011-10-10 23:10 ` Junio C Hamano
2011-10-11 15:39 ` Jakub Narebski
2011-10-11 17:49 ` Junio C Hamano
2011-10-11 18:16 ` Jakub Narebski
2011-10-08 18:31 ` [PATCHv5 2/6] gitweb: Add manpage for gitweb configuration files Jakub Narebski
2011-10-08 18:32 ` [PATCHv5/RFC 3/6] gitweb: Add manpage for gitweb Jakub Narebski
2011-10-10 18:56 ` Junio C Hamano
2011-10-10 22:02 ` Jakub Narebski
2011-10-10 22:18 ` Jonathan Nieder
2011-10-11 13:02 ` Drew Northup
2011-10-11 13:51 ` Jakub Narebski
2011-10-11 14:01 ` [PATCHv5/RFC 3/6] gitweb: Add manpage for gitweb (APPLICATION!!!) Drew Northup
2011-10-11 14:20 ` Jakub Narebski
2011-10-11 16:56 ` Drew Northup
2011-10-08 18:32 ` Jakub Narebski [this message]
2011-10-08 18:32 ` [PATCHv5 5/6] Documentation: Add gitweb config variables to git-config(1) Jakub Narebski
2011-10-08 18:32 ` [PATCHv5 6/6] gitweb: Add gitweb manpages to 'gitweb' package in git.spec Jakub Narebski
2011-10-10 18:47 ` [PATCHv5/RFC 0/6] Moving gitweb documentation to manpages Junio C Hamano
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=1318098723-12813-5-git-send-email-jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).