From: Junio C Hamano <gitster@pobox•com>
To: Drew Northup <n1xim.email@gmail•com>
Cc: "Jakub Narębski" <jnareb@gmail•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: Simplify description of GITWEB_CONFIG_SYSTEM
Date: Mon, 15 Apr 2013 21:36:08 -0700 [thread overview]
Message-ID: <7vobdfnlc7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAM9Z-nmOzpJdT3ni0rYRkg7Z26N5XSRyqp0TkTY79AAZ85pw2A@mail.gmail.com> (Drew Northup's message of "Mon, 15 Apr 2013 23:10:58 -0400")
Drew Northup <n1xim.email@gmail•com> writes:
>> + 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
>> + file (normally /etc/gitweb-common.conf) to keep common default
>> + settings that apply to all instances. Settings from per-instance or
>> system-wide configuration file override those from common system-wide
>> configuration file.
>
> That's the point of explaining SPECIFICALLY why the then current
> behavior wasn't being replaced, and this other mechanism (which would
> otherwise have no obvious reason for existing) was being introduced.
In order to just pick and use the more appropriate one (or a useful
combination of the two), a clean description of what each of them do
without historical cruft is more readable and useful, isn't it? I
would expect that most of them who are newly configuring a system
would pick COMMON one and override per instance as needed, without
touching the SYSTEM one (fallback default) after reading the above,
and that is what we want to happen.
Do you think sysadmins need a history lesson to understand why there
are two different possibilities?
For example, bash reads some but not all possible configuration
files. I would expect .bashrc to be read even for login shells after
reading .bash_login; alas, that is not what happens. The manual
does not apologize that the authors now know better and understand
that it is a stupid behaviour. The order the rc files are read is
just described matter-of-factly, and it gives sufficient information
without unnecessary backstory.
I think the new text conveys the necessary information to the
intended audience with more clarity without the history lesson or
the record of your past frustration. Am I mistaken?
next prev parent reply other threads:[~2013-04-16 4:36 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 [this message]
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
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=7vobdfnlc7.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
--cc=jrnieder@gmail$(echo .)com \
--cc=n1xim.email@gmail$(echo .)com \
--cc=stefano.lattarini@gmail$(echo .)com \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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