From: Jakub Narebski <jnareb@gmail.com>
To: Drew Northup <drew.northup@maine.edu>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCHv5/RFC 3/6] gitweb: Add manpage for gitweb
Date: Tue, 11 Oct 2011 15:51:08 +0200 [thread overview]
Message-ID: <201110111551.09621.jnareb@gmail.com> (raw)
In-Reply-To: <1318338135.22324.33.camel@drew-northup.unet.maine.edu>
On Tue, 11 Oct 2011, Drew Northup wrote:
> On Mon, 2011-10-10 at 17:18 -0500, Jonathan Nieder wrote:
> > Jakub Narebski wrote:
> >
> > > The problem is that catering to old AsciiDoc (but still used by some of
> > > long-term-support Linux distributions) requires to have "SYNOPSIS"
> > > section... but there is no natural synopsis for non self-hostable web
> > > application, is there?
> >
> > I personally think something like
> >
> > SYNOPSIS
> > --------
> > /usr/share/gitweb/gitweb.cgi
> > git instaweb
> >
> > or perhaps something like
> >
> > SYNOPSIS
> > --------
> > http://<site>/?p=<project>.git;a=<action>;h=<object>;<parameters>
> > http://<site>/<project>/<action>/<object>?<parameters>
> >
> > would be best.
>
> This would be why I included a synopsis with my original submission. As
> this was supposed to be a description of the configuration files of said
> application it does not make much sense to put the executable in the
> synopsis. Please forgive me for attempting to make sense!
But this manpage is about _gitweb itself_, not about gitweb config file(s).
Gitweb itself is application, though it is not runnable directly (yet).
Web apps either don't use manpages as documentation, and those that do
that I found (SVN::Web for example) include runnable server-starting script.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2011-10-11 13:51 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 [this message]
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 ` [PATCHv5 4/6] Documentation: Link to gitweb(1) and gitweb.conf(5) in other manpages Jakub Narebski
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=201110111551.09621.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).