From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Priedhorsky, Reid" <reidpr@lanl.gov>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: bug? subprocesses can use wrong Git if $PATH is unset
Date: Sat, 03 Jun 2023 10:38:11 +0900 [thread overview]
Message-ID: <xmqqwn0l72bg.fsf@gitster.g> (raw)
In-Reply-To: <ZHpO9/4RSbeTy0HJ@tapette.crustytoothpaste.net> (brian m. carlson's message of "Fri, 2 Jun 2023 20:20:07 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On 2023-06-02 at 16:14:47, Priedhorsky, Reid wrote:
>> Hello Brian,
>>
>> I do wonder if the behavior would be worth documenting, e.g. at
>> https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables,
>> where Git’s relationship to $HOME is also documented. I would be happy
>> to submit a pull request.
>
> I don't think it's necessary, since it's expected behaviour for me, but
> I am not the only person on this list, and perhaps others would
> appreciate a patch.
I tend to agree that it is an expected behaviour. In addition,
unsetting PATH is not something people deliberately do every day
without understanding its implications, so I would rather not see us
add "if you do this esteric thing, this would happen" for them.
Thanks.
next prev parent reply other threads:[~2023-06-03 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 22:21 bug? subprocesses can use wrong Git if $PATH is unset Priedhorsky, Reid
2023-06-02 0:35 ` brian m. carlson
2023-06-02 16:14 ` Priedhorsky, Reid
2023-06-02 20:20 ` brian m. carlson
2023-06-03 1:38 ` Junio C Hamano [this message]
2023-06-07 17:43 ` Priedhorsky, Reid
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=xmqqwn0l72bg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=reidpr@lanl.gov \
--cc=sandals@crustytoothpaste.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 read-only IMAP folder(s) and NNTP newsgroup(s).