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

Re: [PATCH] gitweb: fallback to system-wide config file if default config does not exist

From
Jakub Narebski <jnareb@gmail.com>
Date
Mar 26, 2008, 19:20 UTC
Message-ID
<fse7mi$pop$1@ger.gmane.org>
In-Reply-To
<20080326181119.25618.qmail@065038ef0fc11c.315fe32.mid.smarden.org>
Gerrit Pape wrote:
Show 12 quoted lines
> From a distribution point of view, configuration files for applications
> should reside in /etc/.  On the other hand it's convenient for multiple
> instances of gitweb (e.g. virtual web servers on a single machine) to have
> a per-instance configuration file, just as gitweb currently supports
> through the file gitweb_config.perl next to the cgi.
> 
> To support both at runtime, this commit introduces GITWEB_CONFIG_SYSTEM as
> a system-wide configuration file which will be used as a fallback if the
> config file sprecified throug GITWEB_CONFIG does not exist.
> 
> See also
>  http://bugs.debian.org/450592
Acked-by: Jakub Narebski <jnareb@gmail.com>
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Gerrit PapeNext: Gerrit Pape
Message 2 of 3 in “gitweb: fallback to system-wide config file if default config does not exist”
  1. gitweb: fallback to system-wide config file if default config does not existGerrit Pape, Mar 26, 2008
  2. Jakub NarebskiMar 26, 2008
  3. gitweb: fallback to system-wide config file if default config does not existGerrit Pape, Apr 5, 2008

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.