git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH/RFCv4 1/4] Documentation: Preparation for gitweb manpages

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Sep 19, 2011, 23:37 UTC
Message-ID
<20110919233703.GF6343@elie>
In-Reply-To
<1316352884-26193-2-git-send-email-jnareb@gmail.com>
Jakub Narebski wrote:
> Gitweb documentation currently consist of gitweb/README, gitweb/INSTALL
> and comments in gitweb source code.  This is harder to find, use and
> browse that manpages ("man gitweb" or "git help gitweb") and HTML
> documentation ("git help --web gitweb").

Language nits: s/consist/consists/; s/that manpages/than manpages/. I completely agree.

> The goal is to move documentation out of gitweb/README to gitweb.txt and
> gitweb.conf.txt manpages, reducing its size 10x from around 500 to
> around 50 lines (two pages), and move information not related drectly to
> building and installing gitweb out of gitweb/INSTALL there.
I guess you mean this patch prepares for or is part of a larger
project or series with that goal?  Wording nits: s/and move
information/and to move information/; s/drectly/directly/; s/ there//.
 
> The idea is to have gitweb manpage sources reside in AsciiDoc format
> in Documentation/ directory, like for gitk and git-gui.  Alternate
> solution would be to have gitweb documentation in gitweb/ directory,
> perhaps in POD format (see perlpod(1)).

Language nits: missing "the" before "Documentation/ directory" and "gitweb manpage sources"; missing "An" before "Alternate solution". I guess this is the most controversial aspect of the patch; your idea seems sane enough to me.

> This patch adds infrastructure for easy generating gitweb-related
> manpages.  It adds currently empty 'gitweb-doc' target to
> Documentation/Makefile, and 'doc' proxy target to gitweb's Makefile.

Language nits: s/easy/easily/; missing "a" before "currently empty 'gitweb-doc' target" and "'doc' proxy target".

Show 7 quoted lines
> This way to build gitweb documentation one can use
>
>   make -C gitweb doc
>
> or
>
>   cd gitweb; make doc
Language nit: a comma after "This way" would disambiguate.

Does "make -CDocumentation man html" build the gitweb documentation, too (and "make install-doc" install it)?

[...]
Show 8 quoted lines
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -170,6 +170,9 @@ info: git.info gitman.info
>  
>  pdf: user-manual.pdf
>  
> +GITWEB_DOC = $(filter gitweb.%,$(DOC_HTML) $(DOC_MAN1) $(DOC_MAN5) $(DOC_MAN7))
> +gitweb-doc: $(GITWEB_DOC)
Looks like no, alas.
Except for that detail, this looks good.

Thanks, Jonathan

Previous: Jakub NarebskiNext: Jakub Narebski
Message 3 of 12 in “Moving gitweb documentation to manpages”
  1. 0/4 Moving gitweb documentation to manpagesJakub Narebski, Sep 18, 2011
  2. 1/4 Documentation: Preparation for gitweb manpagesJakub Narebski, Sep 18, 2011
  3. Jonathan NiederSep 19, 2011
  4. Jakub NarebskiSep 20, 2011
  5. Jakub NarebskiSep 20, 2011
  6. Jonathan NiederSep 20, 2011
  7. Jakub NarebskiSep 20, 2011
  8. 2/4 gitweb: Add manpage for /etc/gitweb.conf (for gitweb documentation)Jakub Narebski, Sep 18, 2011
  9. Jonathan NiederSep 20, 2011
  10. Jakub NarebskiSep 22, 2011
  11. 3/4 gitweb: Add manpage for gitwebJakub Narebski, Sep 18, 2011
  12. 4/4 gitweb: Add gitweb manpages to 'gitweb' package in git.specJakub Narebski, Sep 18, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.