From: "Jakub Narębski" <jnareb@gmail.com>
To: Drew Northup <n1xim.email@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>,
git@vger.kernel.org,
Stefano Lattarini <stefano.lattarini@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: [PATCH] gitweb/INSTALL: GITWEB_CONFIG_SYSTEM is for backward compatibility
Date: Tue, 16 Apr 2013 14:26:01 +0200 [thread overview]
Message-ID: <516D4359.2070501@gmail.com> (raw)
In-Reply-To: <CAM9Z-nm=SUNAHXZtOnz_BSS8VrVYPczicX99FUmDJe6Lj_oKpQ@mail.gmail.com>
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
This can be either squashed with previous patch to gitweb/INSTALL,
kept as separate patch or discarded.
Drew: gitweb(1) or gitweb.conf(5) solution is more involved, so
perhaps something like that?
gitweb/INSTALL | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gitweb/INSTALL b/gitweb/INSTALL
index 7ad1050..386e62f 100644
--- a/gitweb/INSTALL
+++ b/gitweb/INSTALL
@@ -243,7 +243,6 @@ for gitweb (in gitweb/README), and gitweb.conf(5) manpage.
GITWEB_CONFIG_SYSTEM build configuration variable, and override it
through the GITWEB_CONFIG_SYSTEM environment variable.
-
Note that the GITWEB_CONFIG_SYSTEM system-wide configuration file is
only used for instances that lack per-instance configuration file.
You can use GITWEB_CONFIG_COMMON common system-wide configuration
@@ -252,6 +251,8 @@ for gitweb (in gitweb/README), and gitweb.conf(5) manpage.
system-wide configuration file override those from common system-wide
configuration file.
+ (Idiosyncratic GITWEB_CONFIG_SYSTEM is present for backward compatibility.)
+
- The gitweb config file is a fragment of perl code. You can set variables
using "our $variable = value"; text from "#" character until the end
of a line is ignored. See perlsyn(1) for details.
--
1.7.10.4
next prev parent reply other threads:[~2013-04-16 12:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 20:55 [PATCH] Various typofixes Stefano Lattarini
2013-04-11 21:43 ` Eric Sunshine
2013-04-11 22:36 ` [PATCH v2] Fix various typos and grammaros Stefano Lattarini
2013-04-12 0:45 ` Junio C Hamano
2013-04-12 6:48 ` [RFC/PATCH maint 0/10] " Jonathan Nieder
2013-04-12 6:49 ` [PATCH 01/10] doc: various spelling fixes Jonathan Nieder
2013-04-12 19:12 ` Junio C Hamano
2013-04-12 22:20 ` [PATCH] gitweb/INSTALL: Simplify description of GITWEB_CONFIG_SYSTEM Jakub Narębski
2013-04-16 3:10 ` Drew Northup
2013-04-16 4:36 ` Junio C Hamano
2013-04-16 7:11 ` Jakub Narębski
2013-04-16 11:51 ` Drew Northup
2013-04-16 11:56 ` Drew Northup
2013-04-16 12:26 ` Jakub Narębski [this message]
2013-04-16 12:47 ` [PATCH] gitweb/INSTALL: GITWEB_CONFIG_SYSTEM is for backward compatibility Drew Northup
2013-04-16 12:52 ` Drew Northup
2013-04-16 22:26 ` Jonathan Nieder
2013-04-18 1:00 ` Drew Northup
2013-04-18 1:44 ` Junio C Hamano
2013-04-12 6:50 ` [PATCH 02/10] git-remote-mediawiki: spelling fixes Jonathan Nieder
2013-04-12 11:16 ` Matthieu Moy
2013-04-12 6:54 ` [PATCH 03/10] contrib/subtree: fix spelling of accidentally Jonathan Nieder
2013-04-12 6:57 ` [PATCH 04/10] obstack: fix spelling of similar Jonathan Nieder
2013-04-12 7:01 ` [PATCH 05/10] compat/regex: fix spelling and grammar in comments Jonathan Nieder
2013-04-12 7:06 ` [PATCH 06/10] compat/nedmalloc: fix spelling " Jonathan Nieder
2013-04-12 7:17 ` Sebastian Schuberth
2013-04-12 7:07 ` [PATCH 07/10] precompose-utf8: fix spelling of "want" in error message Jonathan Nieder
2013-04-12 7:09 ` [PATCH 08/10] kwset: fix spelling in comments Jonathan Nieder
2013-04-12 7:10 ` [PATCH 09/10] git-gui: " Jonathan Nieder
2013-04-12 7:11 ` [PATCH 10/10] Correct common spelling mistakes in comments and tests Jonathan Nieder
2013-04-12 20:39 ` Junio C Hamano
2013-04-12 16:09 ` [RFC/PATCH maint 0/10] Re: [PATCH v2] Fix various typos and grammaros Junio C Hamano
2013-04-12 8:16 ` Stefano Lattarini
2013-04-12 16:10 ` 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=516D4359.2070501@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=n1xim.email@gmail.com \
--cc=stefano.lattarini@gmail.com \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.