From: Matt Rogers <mattr94@gmail.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: "Mateusz Nowotyński" <maxmati4@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
bwilliams.eng@gmail.com
Subject: Re: [PATCH] config: use GIT_CONFIG in git config sequence
Date: Sun, 26 Apr 2020 09:30:13 -0400 [thread overview]
Message-ID: <CAOjrSZt7WJy1vv97Rw9MFJyTcB2Ehqq9BjGrXMtV95oB5p53SA@mail.gmail.com> (raw)
In-Reply-To: <ff9a63d4-80e4-8090-c85c-03fd3ab43c55@iee.email>
> Given the extra config environment settings, could/should the
> --show-scope (or complementary option) also show/clarify these
> environment variable settings?
I'm lukewarm either way on this one, I think it would be pretty trivial
to write something that did this, so that only leaves the question of
'should' we do this, which I don't really have any particularly strong
feelings about. What would this even ultimately look like? perhaps
something like this for a command of `git config --show-scope`:
system var=option (currently ignored due to GIT_CONFIG_NOSYSTEM)
Which kind of begs the question of how many people set that variable
and then forget that they set it? Although I can totally see why it would
be nice to have some kind of config flag that's a big
"Just show me everything that's going on option" which considering these
variables would probably be a little bit more than the current next-best of
`git config --list --show-scope --show-origin`. Again though, I'm not
exactly sure how useful such an option would be.
--
Matthew Rogers
next prev parent reply other threads:[~2020-04-26 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 23:57 [PATCH] config: use GIT_CONFIG in git config sequence Mateusz Nowotyński
2020-04-26 0:16 ` Junio C Hamano
2020-04-26 9:58 ` Philip Oakley
2020-04-26 19:32 ` Mateusz Nowotyński
2020-04-26 20:08 ` brian m. carlson
2020-04-27 20:04 ` Mateusz Nowotynski
2020-04-26 21:01 ` Junio C Hamano
2020-04-26 1:12 ` Matt Rogers
2020-04-26 10:00 ` Philip Oakley
2020-04-26 13:30 ` Matt Rogers [this message]
2020-04-26 20:04 ` Philip Oakley
2020-04-26 21:16 ` Junio C Hamano
2020-04-26 22:32 ` Junio C Hamano
2020-04-27 19:39 ` Mateusz Nowotynski
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=CAOjrSZt7WJy1vv97Rw9MFJyTcB2Ehqq9BjGrXMtV95oB5p53SA@mail.gmail.com \
--to=mattr94@gmail.com \
--cc=bwilliams.eng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=maxmati4@gmail.com \
--cc=philipoakley@iee.email \
/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).