From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Elsie Hupp <git@elsiehupp.com>, git@vger.kernel.org
Subject: Re: Multiple --global config workspaces?
Date: Tue, 11 Oct 2022 09:13:35 -0400 [thread overview]
Message-ID: <Y0Vr/4IeA236nxzF@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqwn96x61t.fsf@gitster.g>
On Mon, Oct 10, 2022 at 10:50:22PM -0700, Junio C Hamano wrote:
> One way to do this would be to have
>
> [includeIf "gitdir:~/Repositories/github/"] path = $HOME/.githubconfig
> [includeIf "gitdir:~/Repositories/gitlab/"] path = $HOME/.gitlabconfig
>
> in $HOME/.gitconfig and then write in these two extra files that are
> conditionally included whatever settings you want to use for any and
> all repositories that come from GitHub or GitLab.
I was about to write the same response. :) One small correction, though:
we don't expand $HOME in include paths. You can use "~", but easier
still is that non-absolute includes are relative to the including file.
Relative paths in includes are relative to the including file. So you
can just write ".githubconfig", etc, and we'll expect them adjacent to
$HOME/.gitconfig (or the xdg path if you use that, I guess).
-Peff
next prev parent reply other threads:[~2022-10-11 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 3:06 Multiple --global config workspaces? Elsie Hupp
2022-10-11 5:50 ` Junio C Hamano
2022-10-11 13:13 ` Jeff King [this message]
2022-10-11 16:55 ` Elsie Hupp
2022-10-11 18:41 ` Elsie Hupp
2022-10-14 19:39 ` Jeff King
2022-10-15 10:56 ` Matthias Aßhauer
2022-10-15 18:14 ` Jeff King
2022-10-18 4:02 ` Elsie Hupp
2022-10-18 20:53 ` Jeff King
2022-10-20 2:29 ` Elsie Hupp
2022-10-20 2:39 ` Elsie Hupp
2022-10-11 13:56 ` Philip Oakley
2022-10-11 5:51 ` Reto
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=Y0Vr/4IeA236nxzF@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@elsiehupp.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 read-only IMAP folder(s) and NNTP newsgroup(s).