git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Is there interest in reading ~/.gitconfig.d/* and /etc/gitconfig.d/*?
Date: Thu, 1 Apr 2010 21:20:46 +0000	[thread overview]
Message-ID: <z2s51dd1af81004011420ka5d3a800kf6b3e4591527fc12@mail.gmail.com> (raw)

I've patched Git to read ~/.gitconfig.d/* and /etc/gitconfig.d/* in
addition to reading ~/.gitconfig and /etc/gitconfig where it would
normally do so. the gitconfig.d/* files are read in numeric sort order
as is the custom with such files and read after the main .gitconfig
file so they override it.

This is very useful for me because I maintain my .gitconfig in a
public git repository but I don't want anyone to know my github.token.
Because of that I have to do a little song & dance every time I commit
to the file (if the token is part of the diff) or pull to the file (to
not encounter a merge conflict).

This would also facilitate neat stuff like easily using bits of other
people's gitconfig libraries by cloning their repository somewhere and
symlinking their .gitconfig to ~/.gitconfig.d/99-some-library.

I'm not attaching my patch because it would be inhumane to subject
anyone to it in its current state. However, I'd like to ask if there's
any interest in getting a proper & documented patch for this. If so I
can submit a proper patch, if not I can just continue to patch my Git
build with my hack.

Apologies if this has been brought up before. I tried to search for
prior art but ".gitconfig.d" makes for a really bad search query in
all the search engines I could find that index this list.

             reply	other threads:[~2010-04-01 21:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 21:20 Ævar Arnfjörð Bjarmason [this message]
2010-04-01 22:03 ` Is there interest in reading ~/.gitconfig.d/* and /etc/gitconfig.d/*? Heiko Voigt
2010-04-04  7:24 ` Peter Krefting
2010-04-04  7:59   ` Eli Barzilay
     [not found]   ` <19384.17579.205005.86711@winooski.ccs.neu.edu>
2010-04-06  8:15     ` Ævar Arnfjörð Bjarmason
2010-04-06  9:02       ` Jakub Narebski
2010-05-06 21:14       ` [PATCH/RFC] Hacky version of a glob() driven config include Ævar Arnfjörð Bjarmason
2010-05-07  6:00         ` Bert Wesarg
2010-05-07 16:56           ` Ævar Arnfjörð Bjarmason
2010-05-07 18:29             ` Bert Wesarg
2010-05-07 18:58               ` Ævar Arnfjörð Bjarmason
2010-05-07 19:02                 ` Jacob Helwig
2010-05-07 19:52                 ` Bert Wesarg
2010-05-07 20:11                   ` [PATCH/RFC v2] " Ævar Arnfjörð Bjarmason
2010-05-07 20:46         ` [PATCH/RFC] " Jakub Narebski
2010-05-07 22:15           ` Ævar Arnfjörð Bjarmason
2010-05-07 23:43             ` Jakub Narebski
2010-05-08  2:30               ` Ping Yin
2010-05-08  8:18                 ` Jakub Narebski
2010-05-08  9:03                   ` Ping Yin
2010-05-08  5:06         ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=z2s51dd1af81004011420ka5d3a800kf6b3e4591527fc12@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).