From: Taylor Blau <me@ttaylorr.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
German Lashevich <german.lashevich@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 1/3] doc/git-config: explain --file instead of referring to GIT_CONFIG
Date: Wed, 14 Jul 2021 18:20:30 -0400 [thread overview]
Message-ID: <YO9jLvGlIVj3aI/m@nand.local> (raw)
In-Reply-To: <YO9ZGTX9f1fOpTkh@coredump.intra.peff.net>
On Wed, Jul 14, 2021 at 05:37:29PM -0400, Jeff King wrote:
> -f config-file::
> --file config-file::
> - Use the given config file instead of the one specified by GIT_CONFIG.
> + For writing options: write to the specified file rather than the
> + repository `.git/config`.
I wonder whether or not we should write "rather than the repository
`$GIT_DIR/config`" instead of `.git/config`. The former is true for bare
repositories, too, but may in fact be more confusing than what you have
writen so clearly.
Perhaps `.git/config` is clear enough; I definitely don't feel strongly
about it.
Thanks,
Taylor
next prev parent reply other threads:[~2021-07-14 22:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 17:10 Bug report: GIT_CONFIG and user.email/name German Lashevich
2021-07-14 18:10 ` Jeff King
2021-07-14 18:26 ` German Lashevich
2021-07-14 20:47 ` Junio C Hamano
2021-07-14 21:36 ` Jeff King
2021-07-14 21:37 ` [PATCH 1/3] doc/git-config: explain --file instead of referring to GIT_CONFIG Jeff King
2021-07-14 22:20 ` Taylor Blau [this message]
2021-07-14 22:23 ` Jeff King
2021-07-14 22:26 ` Taylor Blau
2021-07-20 19:34 ` Martin Ågren
2021-07-20 20:01 ` Jeff King
2021-07-20 20:03 ` Jeff King
2021-07-20 21:55 ` Junio C Hamano
2021-07-14 21:38 ` [PATCH 2/3] doc/git-config: clarify GIT_CONFIG environment variable Jeff King
2021-07-14 21:38 ` [PATCH 3/3] doc/git-config: simplify "override" advice for FILES section Jeff King
2021-07-14 22:22 ` Bug report: GIT_CONFIG and user.email/name Taylor Blau
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=YO9jLvGlIVj3aI/m@nand.local \
--to=me@ttaylorr.com \
--cc=german.lashevich@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).