From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: fallback to system-wide config file if default config does not exist
Date: Wed, 26 Mar 2008 20:20:52 +0100 [thread overview]
Message-ID: <fse7mi$pop$1@ger.gmane.org> (raw)
In-Reply-To: 20080326181119.25618.qmail@065038ef0fc11c.315fe32.mid.smarden.org
Gerrit Pape wrote:
> 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
next prev parent reply other threads:[~2008-03-26 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 18:11 [PATCH] gitweb: fallback to system-wide config file if default config does not exist Gerrit Pape
2008-03-26 19:20 ` Jakub Narebski [this message]
2008-04-05 16:37 ` [PATCH amend] " Gerrit Pape
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='fse7mi$pop$1@ger.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.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).