From: Junio C Hamano <gitster@pobox.com>
To: Stefan Haller <lists@haller-berlin.de>
Cc: git@vger.kernel.org
Subject: Re: Storing private config files in .git directory?
Date: Mon, 08 Jan 2024 10:20:00 -0800 [thread overview]
Message-ID: <xmqq34v7lmb3.fsf@gitster.g> (raw)
In-Reply-To: <8e344dee-f84e-4a2c-835a-406ee72d129b@haller-berlin.de> (Stefan Haller's message of "Sun, 7 Jan 2024 14:03:20 +0100")
Stefan Haller <lists@haller-berlin.de> writes:
> Our git client (lazygit) has a need to store per-repo config files that
> override the global one, much like git itself. The easiest way to do
> that is to store those in a .git/lazygit.cfg file, and I'm wondering if
> there's any reason why this is a bad idea?
An obvious alternative is to have .lazygit directory next to .git directory
which would give you a bigger separation, which can cut both ways.
next prev parent reply other threads:[~2024-01-08 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 13:03 Storing private config files in .git directory? Stefan Haller
2024-01-08 18:20 ` Junio C Hamano [this message]
2024-01-10 11:08 ` Jeff King
2024-01-11 13:28 ` Stefan Haller
2024-01-12 6:56 ` Jeff King
2024-01-08 18:56 ` Konstantin Ryabitsev
2024-01-08 19:48 ` Marc Branchaud
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=xmqq34v7lmb3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lists@haller-berlin.de \
/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).