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

Re: [PATCHv3 2/5] gitweb: Describe CSSMIN and JSMIN in gitweb/INSTALL

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jun 6, 2011, 20:01 UTC
Message-ID
<20110606200126.GB30588@elie>
In-Reply-To
<1307382271-7677-3-git-send-email-jnareb@gmail.com>
Jakub Narebski wrote:
Show 5 quoted lines
> The build-time configuration variables JSMIN and CSSMIN were mentioned
> only in Makefile; add their description to gitweb/INSTALL.
>
> This required moving description of GITWEB_JS up, near GITWEB_CSS and
> just introduced CSMIN and JSMIN.

Why does this require that? Ah, to make the analogy with GITWEB_CSS clear and because the JSMIN description refers to it.

> --- a/gitweb/INSTALL
> +++ b/gitweb/INSTALL
> @@ -147,6 +147,19 @@ You can specify the following configuration variables when building GIT:
[...]
Show 7 quoted lines
> + * CSSMIN, JSMIN
> +   Invocation of a CSS minifier or a JavaScript minifier, respectively,
> +   working as a filter (source on standard input, minified result on
> +   standard output).  If set, it is used to generate a minified version of
> +   'static/gitweb.css' or 'static/gitweb.js', respectively.  *Note* that
> +   minified files would have *.min.css and *.min.js extension, which is
> +   important if you also set GITWEB_CSS and/or GITWEB_JS.  [No default]

When I first read this, I thought it meant these command lines were going to be cooked into the gitweb script and invoked at run time. Maybe (sorry for the rough text):

* CSSMIN, JSMIN
  Command for a CSS minifier or a Javascript minifier, working as a
  filter [...]
  These are used if defined to generate smaller, non human-readable
  versions of 'gitweb/gitweb.css' and 'static/gitweb.js' at
  'static/gitweb.min.css' and 'static/gitweb.min.js'.  Only the minified
  versions are installed, which is important if you also set GITWEB_CSS
  or GITWEB_JS.  [No default]
Aside from that, looks good.  Thanks.
Previous: Jakub NarebskiNext: Jakub Narebski
Message 5 of 23 in “[RFC/PATCHv3 0/5] Improving gitweb documentation, creating manpages”
  1. Jakub NarebskiJun 6, 2011
  2. 1/5 gitweb: Move information about installation from README to INSTALLJakub Narebski, Jun 6, 2011
  3. Jonathan NiederJun 6, 2011
  4. 2/5 gitweb: Describe CSSMIN and JSMIN in gitweb/INSTALLJakub Narebski, Jun 6, 2011
  5. Jonathan NiederJun 6, 2011
  6. Jakub NarebskiJun 8, 2011
  7. 3/5 gitweb: Move "Requirements" up in gitweb/INSTALLJakub Narebski, Jun 6, 2011
  8. Jonathan NiederJun 6, 2011
  9. 4/5 gitweb: Starting work on a man page for /etc/gitweb.conf (WIP)Jakub Narebski, Jun 6, 2011
  10. Jonathan NiederJun 6, 2011
  11. Jonathan NiederJun 6, 2011
  12. Jakub NarebskiJun 8, 2011
  13. Drew NorthupJun 7, 2011
  14. Jonathan NiederJun 7, 2011
  15. Drew NorthupJun 7, 2011
  16. Jakub NarebskiJun 7, 2011
  17. Junio C HamanoJun 7, 2011
  18. Drew NorthupJun 7, 2011
  19. Jakub NarebskiJun 7, 2011
  20. Drew NorthupJun 7, 2011
  21. Jakub NarebskiJun 10, 2011
  22. Jakub NarebskiJun 8, 2011
  23. 5/5 gitweb: Starting work on a man page for gitweb (WIP)Jakub Narebski, Jun 6, 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.