From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: David Glasser <glasser@davidglasser.net>, git@vger.kernel.org
Subject: Re: git-config(1) should mention `git -c`
Date: Tue, 23 Aug 2016 10:16:18 -0700 [thread overview]
Message-ID: <xmqqpoozwgm5.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160822185709.izdfbkbsmeip5u7c@sigill.intra.peff.net> (Jeff King's message of "Mon, 22 Aug 2016 14:57:09 -0400")
Jeff King <peff@peff.net> writes:
> That seems like the most sensible place, as that is where we should
> cover the order of reading and precedence. Perhaps FILES should be
> renamed to SOURCES or something (though I do not recall if we are
> restricted to "usual" manpage section names or not).
>
> Arguably this is not about git-config the program at all, but the
> general concept of "configuration for git", because the precedence rules
> apply equally to all of the git programs that read config.
True, but that argument leads us to say git(1) is the best place ;-)
If the user wants to know "how does the configuration values get
read?", and wishes not having to go around fishing for the
information in multiple places (and I think that is a reasonable
thing to wish for), I think adding it to the FILES section of
git-config(1) is a better option than inventing a separate
gitconfig(7), which would still require the user to consult two
places.
next prev parent reply other threads:[~2016-08-23 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 18:42 git-config(1) should mention `git -c` David Glasser
2016-08-22 18:57 ` Jeff King
2016-08-23 17:16 ` Junio C Hamano [this message]
2016-08-23 17:33 ` David Glasser
2016-08-23 21:41 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpoozwgm5.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=glasser@davidglasser.net \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).