From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git.txt: update description of the configuration mechanism
Date: Thu, 14 Feb 2013 08:52:53 -0800 [thread overview]
Message-ID: <7vhale3kii.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1360856214-934-1-git-send-email-Matthieu.Moy@imag.fr> (Matthieu Moy's message of "Thu, 14 Feb 2013 16:36:54 +0100")
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> The old Git version where it appeared is not useful only to historians,
> not to normal users.
That statement cannot be generally true, unless the "old" is really
old and no longer relevant but 0.99.9 is sufficiently old so the
value of the part of the message you removed that warns users with
ancient versions that they may not be able to use the feature
without upgrading has diminished.
> +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.
Both look sensible.
prev parent reply other threads:[~2013-02-14 16:53 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
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 [this message]
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=7vhale3kii.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
/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).