From: Drew Northup <n1xim.email@gmail.com>
To: "Jakub Narębski" <jnareb@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: Re: [PATCH] gitweb/INSTALL: GITWEB_CONFIG_SYSTEM is for backward compatibility
Date: Tue, 16 Apr 2013 08:47:09 -0400 [thread overview]
Message-ID: <CAM9Z-nkbBS5qvbkocdGWj7rwtSxB86+R4jdjcBOxCU4YjtgZ1A@mail.gmail.com> (raw)
In-Reply-To: <516D4359.2070501@gmail.com>
On Tue, Apr 16, 2013 at 8:26 AM, Jakub Narębski <jnareb@gmail.com> wrote:
> Drew: gitweb(1) or gitweb.conf(5) solution is more involved, so
> perhaps something like that?
That or: (or both I suppose....hopefully not too mangled by Google's
mail gadget)
-- >8 --
Subject: [PATCH] Documentation/gitweb.conf.txt: Move note about config
order precedence
To go along with Jakub Narebski's cleanup of gitweb/INSTALL; making
it clear that gitweb's config files work differently than a lot of
other system-wide software. This is unobtrusive yet to the point.
---
Documentation/gitweb.conf.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/gitweb.conf.txt b/Documentation/gitweb.conf.txt
index eb63631..05c81e7 100644
--- a/Documentation/gitweb.conf.txt
+++ b/Documentation/gitweb.conf.txt
@@ -55,7 +55,8 @@ following order:
then fallback system-wide configuration file (defaults to
'/etc/gitweb.conf').
Values obtained in later configuration files override values obtained earlier
-in the above sequence.
+in the above sequence. This is different from many system-wide software
+installations and will stay this way for historical reasons.
Locations of the common system-wide configuration file, the fallback
system-wide configuration file and the per-instance configuration file
--
1.8.0
--
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
next prev parent reply other threads:[~2013-04-16 12:47 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 ` [PATCH] gitweb/INSTALL: GITWEB_CONFIG_SYSTEM is for backward compatibility Jakub Narębski
2013-04-16 12:47 ` Drew Northup [this message]
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=CAM9Z-nkbBS5qvbkocdGWj7rwtSxB86+R4jdjcBOxCU4YjtgZ1A@mail.gmail.com \
--to=n1xim.email@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=jrnieder@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 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).