From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: [BUG] PREFIX environment variable ignored by git config --system
Date: Wed, 29 Jan 2025 15:36:48 -0800 [thread overview]
Message-ID: <xmqqwmedgpkf.fsf@gitster.g> (raw)
In-Reply-To: <009c01db728d$164a60d0$42df2270$@nexbridge.com> (rsbecker@nexbridge.com's message of "Wed, 29 Jan 2025 15:33:36 -0500")
<rsbecker@nexbridge.com> writes:
> On January 29, 2025 3:15 PM, Junio C Hamano wrote:
>><rsbecker@nexbridge.com> writes:
>>
>>> The documentation on the Environment Configuration page seems to imply
>>> that
>>
>>Sorry, I am totally lost. Whose documentation on what software are you
> referring
>>to?
>>
>> $ git grep -i -e 'environment configuration'
>>
>>comes back empty.
>
> It is here:
> https://git-scm.com/book/ms/v2/Git-Internals-Environment-Variables
It is news to me ;-).
$ git grep '[^_]PREFIX[^_]'
does not have any hits in the source, so I do not see how we _could_
be paying any attention to such a thing.
The description seems to originate at
https://github.com/progit2-ms/progit2/commit/c24f22d6a6b0572f5756afd64f0c2e9fa6f804fa
that was more than 10 years old. I do not know how reliable the
description there is.
next prev parent reply other threads:[~2025-01-29 23:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 16:34 [BUG] PREFIX environment variable ignored by git config --system rsbecker
2025-01-29 16:41 ` Junio C Hamano
2025-01-29 17:01 ` rsbecker
2025-01-29 20:15 ` Junio C Hamano
2025-01-29 20:33 ` rsbecker
2025-01-29 23:36 ` Junio C Hamano [this message]
2025-01-29 23:49 ` rsbecker
2025-01-29 23:53 ` Junio C Hamano
2025-01-30 0:07 ` rsbecker
2025-01-30 0:23 ` Junio C Hamano
2025-01-30 0:37 ` rsbecker
2025-01-30 19:37 ` Ben Knoble
2025-01-30 21:57 ` Junio C Hamano
2025-01-29 18:20 ` rsbecker
2025-01-29 23:48 ` Junio C Hamano
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=xmqqwmedgpkf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
/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).