From: Jakub Narebski <jnareb@gmail.com>
To: "J.H." <warthog9@kernel.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Drew Northup <drew.northup@maine.edu>,
git@vger.kernel.org, Petr Baudis <pasky@suse.cz>
Subject: Re: [PATCH/WIP] Starting work on a man page for /etc/gitweb.conf
Date: Thu, 12 May 2011 20:17:51 +0200 [thread overview]
Message-ID: <201105122017.52373.jnareb@gmail.com> (raw)
In-Reply-To: <4DCC17BE.7000005@kernel.org>
On Thu, 12 May 2011, J.H. wrote:
> Beyond that I've no real issue that haven't already been brought up, but
> I do want to make sure that the ultimate plan here is to add the scripts
> that generate this vs. the final output, right? I mean we already have
> 2 places this documentation lives (in gitweb.perl and README), I'm not
> sure we need a 3rd place to update the documentation at by hand. Just
> asking.
I think the ultimate goal is to move _documentation_ out of gitweb/README
(and some from gitweb/INSTALL) to gitweb.txt (or gitweb.pod) and
gitweb.conf.txt manpages... so that gitweb/README would be of size of
other README's (with sole exception of t/README, which is special case),
i.e. up to around 2,300 lines, and not 23,000 lines (10 times more).
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2011-05-12 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 19:21 [PATCH/WIP] Starting work on a man page for /etc/gitweb.conf Drew Northup
2011-05-12 10:53 ` Jonathan Nieder
2011-05-12 15:01 ` Jakub Narebski
2011-05-12 17:03 ` Drew Northup
2011-05-12 17:24 ` J.H.
2011-05-12 18:16 ` Drew Northup
2011-05-12 18:17 ` Jakub Narebski [this message]
2011-05-12 18:08 ` Jakub Narebski
2011-05-12 18:33 ` Drew Northup
2011-05-12 19:01 ` Jakub Narebski
2011-05-15 10:34 ` [RFC/PATCH] 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=201105122017.52373.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).