From: Michael J Gruber <git@drmicha.warpmail.net>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] git.txt: update description of the configuration mechanism
Date: Thu, 14 Feb 2013 17:15:04 +0100 [thread overview]
Message-ID: <511D0D88.6010302@drmicha.warpmail.net> (raw)
In-Reply-To: <1360856214-934-1-git-send-email-Matthieu.Moy@imag.fr>
Matthieu Moy venit, vidit, dixit 14.02.2013 16:36:
> The old Git version where it appeared is not useful only to historians,
> not to normal users. Also, the text was mentioning only the per-repo
I do not think you meant to not remove so many nots ;)
Besides, if history is uninteresting, then so is sociology: "familiar to
some people" can go, too.
> config file, so add a mention of ~/.gitconfig. Describing in details the
> system-wide, XDG and all would be counter-productive here, so reword the
Hmpf, I think this gives a way too prominent role to "~/.gitconfig". The
config files most people will have to deal with are:
- the repo config file
- the one set by "config --global"
And really, it would often be best if the latter was the XDG thing.
So, I'm all for improving git.txt, but somewhat differently ;)
> description of the link to git-config to make it clear that it is not
> only a list of configuration options.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
> ---
> Documentation/git.txt | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/git.txt b/Documentation/git.txt
> index 0b681d9..e332947 100644
> --- a/Documentation/git.txt
> +++ b/Documentation/git.txt
> @@ -535,10 +535,11 @@ include::cmds-purehelpers.txt[]
> Configuration Mechanism
> -----------------------
>
> -Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file
> -is used to hold per-repository configuration options. It is a
> -simple text file modeled after `.ini` format familiar to some
> -people. Here is an example:
> +Git uses a simple text file format modeled after `.ini` format
> +familiar to some people to store its configuration. The `.git/config`
> +file is used to hold per-repository configuration options, and
> +per-user configuration can be stored in a `~/.gitconfig` file.
> +Here is an example:
>
> ------------
> #
> @@ -559,7 +560,7 @@ people. Here is an example:
>
> Various commands read from the configuration file and adjust
> their operation accordingly. See linkgit:git-config[1] for a
> -list.
> +list and more details about the configuration mechanism.
>
>
> Identifier Terminology
>
next prev parent reply other threads:[~2013-02-14 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 15:36 [PATCH] git.txt: update description of the configuration mechanism Matthieu Moy
2013-02-14 16:15 ` Michael J Gruber [this message]
2013-02-14 16:23 ` Matthieu Moy
2013-02-14 17:10 ` Junio C Hamano
2013-02-14 17:36 ` Matthieu Moy
2013-02-14 18:03 ` Junio C Hamano
2013-02-15 8:18 ` Michael J Gruber
2013-02-14 16:52 ` 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=511D0D88.6010302@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).