git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] PREFIX environment variable ignored by git config --system
Date: Wed, 29 Jan 2025 19:07:38 -0500	[thread overview]
Message-ID: <001501db72aa$fc812350$f58369f0$@nexbridge.com> (raw)
In-Reply-To: <xmqqfrl1gosc.fsf@gitster.g>

On January 29, 2025 6:54 PM, Junio C Hamano wrote:
><rsbecker@nexbridge.com> writes:
>
>> Those of us who have written documentation for much of our lives,
>> really miss accuracy. There are companies where a wrong bit of
>> documentation is considered as high severity defect. Regardless of that...
>
>The association with that "book" and those who hang around here is that we could
>contribute corrections to them, as they are open source and we are friends, but
>that is about it ;-).
>
>I am reasonably sure that they will appreciate a well researched pull request (and
>"well reserached" does not mean "somebody says this is incorrect" but needs a bit
>more than that).

Well, we are all friends here 😉 

Be that as it may, the following seems to work:

$ GIT_CONFIG_SYSTEM=/home/randall/etc/gitconfig git config --system --list
fatal: unable to read config file '/home/randall/etc/gitconfig': No such file or directory

This appears to do exactly what I am looking for. When I create that file, git picks
up config values from that file.The question is, is this environment variable actually
sanctioned or is it just coincidence? It does exactly what I am looking for.


  reply	other threads:[~2025-01-30  0:07 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
2025-01-29 23:49           ` rsbecker
2025-01-29 23:53             ` Junio C Hamano
2025-01-30  0:07               ` rsbecker [this message]
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='001501db72aa$fc812350$f58369f0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).