From: "Jakub Narębski" <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Drew Northup <n1xim.email@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: Tue, 16 Apr 2013 09:11:10 +0200 [thread overview]
Message-ID: <516CF98E.2050706@gmail.com> (raw)
In-Reply-To: <7vobdfnlc7.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> 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?
[...]
> 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?
Note also that this is about *gitweb/INSTALL*, which is meant to be
*short* and succint description on how to install gitweb, and not
about the reference documentation: gitweb(1) or gitweb.conf(5).
Description of historical behavior (and backward compatibility)
has place (if any) in manpages, not gitweb/INSTALL.
--
Jakub Narębski
next prev parent reply other threads:[~2013-04-16 7:11 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 [this message]
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=516CF98E.2050706@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.