From: Jeff King <peff@peff.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: curious about wording in "man git-config", ENVIRONMENT
Date: Tue, 26 Jun 2018 08:43:16 -0400 [thread overview]
Message-ID: <20180626124316.GA15419@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.2.21.1806260608270.6007@localhost.localdomain>
On Tue, Jun 26, 2018 at 06:18:26AM -0400, Robert P. J. Day wrote:
>
> ENVIRONMENT
> GIT_CONFIG
> Take the configuration from the given file instead of
> .git/config. Using the "--global" option forces this to
> ~/.gitconfig. Using the "--system" option forces this to
> $(prefix)/etc/gitconfig.
>
> is the phrase "forces this to" really what you want to use here?
> maybe i misunderstand what this option does, doesn't it simply mean
> that it will use a different (specified) file from the default,
> depending on the context (local, global, system)?
>
> it just seems weird to say that the option "forces" the use of what
> are clearly the default files. thoughts?
I agree it's weird. I think it's trying to mean "behaves as if it was
set to", but with the additional notion that the command-line argument
would take precedence over the environment (which is our usual rule).
But then we should just say those things explicitly.
Just looking at mentions of GIT_CONFIG in that manpage and knowing the
history, I think:
- the environment section should say something like:
GIT_CONFIG
If set and no other specific-file options are given, behaves as
if `--file=$GIT_CONFIG` was provided on the command-line.
- possibly the manpage should mention that GIT_CONFIG is historical and
should not be used in new code (we could also consider an actual
deprecation period and removal of the feature, though aside from
documentation confusion I do not think it is hurting anyone)
- the description of --file should not mention it at all. Instead it
should reference the "FILES" section which describes the whole lookup
sequence
- mention of GIT_CONFIG should be dropped from the FILES section. We
don't want to point people towards using it. And if they come across
it in the wild, they can find it in the ENVIRONMENT section.
- references to "--global" should stop mentioning ~/.gitconfig,
since in a post-XDG world it could be elsewhere (they're better to
refer to the "--global" description or the FILES section)
- references to "--system" should stop mentioning $(prefix)/etc/gitconfig,
since it can be configured separately from the prefix (and in most
packaged builds which set prefix=/usr, $(sysconfdir) is not
$(prefix)/etc).
-Peff
next prev parent reply other threads:[~2018-06-26 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 10:18 curious about wording in "man git-config", ENVIRONMENT Robert P. J. Day
2018-06-26 12:43 ` Jeff King [this message]
2018-06-26 16:51 ` Robert P. J. Day
2018-06-28 18:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180626124316.GA15419@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).