git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: John 'Warthog9' Hawley <warthog9@kernel.org>,
	Petr Baudis <pasky@suse.cz>,
	Drew Northup <drew.northup@maine.edu>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Jakub Narebski <jnareb@gmail.com>
Subject: [RFC/PATCHv2 0/2] Starting work on man pages for gitweb and gitweb.conf (WIP)
Date: Sun, 29 May 2011 21:50:24 +0200	[thread overview]
Message-ID: <1306698626-32402-1-git-send-email-jnareb@gmail.com> (raw)

This is very much work in progress.  

1. The man page for /etc/gitweb.conf is modified, extended and
improved version of patch by Drew Northup from

  "[PATCH/WIP] Starting work on a man page for /etc/gitweb.conf"
  http://thread.gmane.org/gmane.comp.version-control.git/173422

Drew version was mostly pulled directly from the README and INSTALL
files of gitweb.  I have tried to incorporate comments in mentioned
thread, and to group config variables by category.

2. The man page for gitweb is slightly extended version of patch I
have sent to git mailing list as

  "[RFC/PATCH] gitweb: Starting work on a man page for gitweb (WIP)"
  http://thread.gmane.org/gmane.comp.version-control.git/173422/focus=173625


NOTE that I have only tested that both generated manpages _looks_
(halfway) reasonable.  I didn't check HTML output.

The major part that is left (besides extending both manpages with new
information) is actually de-duplicate contents, i.e. delete those
parts of gitweb/README and gitweb/INSTALL that were copied to those
new manpages.

Both of those are also available in 'gitweb/doc' branch in one of my
repositories:

  git://repo.or.cz/git/jnareb-git.git
  git://github.com/jnareb/git.git


Shortlog:
~~~~~~~~~
Drew Northup (1):
  Starting work on a man page for /etc/gitweb.conf (WIP)

Jakub Narebski (1):
  gitweb: Starting work on a man page for gitweb (WIP)

Diffstat:
~~~~~~~~~
 Documentation/Makefile        |    4 +-
 Documentation/gitweb.conf.txt |  436 +++++++++++++++++++++++++++++++++++++++++
 Documentation/gitweb.txt      |  334 +++++++++++++++++++++++++++++++
 git.spec.in                   |    3 +
 gitweb/Makefile               |   14 ++
 5 files changed, 789 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/gitweb.conf.txt
 create mode 100644 Documentation/gitweb.txt

-- 
1.7.5

             reply	other threads:[~2011-05-29 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 19:50 Jakub Narebski [this message]
2011-05-29 19:50 ` [RFC/PATCHv2 1/2] Starting work on a man page for /etc/gitweb.conf (WIP) Jakub Narebski
2011-05-29 20:37   ` Junio C Hamano
2011-05-29 20:58     ` Jakub Narebski
2011-05-29 19:50 ` [RFC/PATCHv2 2/2] gitweb: Starting work on a man page for gitweb (WIP) 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=1306698626-32402-1-git-send-email-jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=pasky@suse.cz \
    --cc=warthog9@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;
as well as URLs for NNTP newsgroup(s).