Re: [PATCH 0/2] Introduce ~/.gitconfig
- From
Alex Riesen <raa.lkml@gmail.com>
- Date
- Jun 8, 2006, 14:49 UTC
- Message-ID
- <81b0412b0606080749k25a306cetf44a50836998ae09@mail.gmail.com>
- In-Reply-To
- <1149775348.23938.236.camel@cashmere.sps.mot.com>
On 6/8/06, Jon Loeliger <jdl@freescale.com> wrote:
> --repo into $GIT_DIR/.gitconfig <- current default, right? > --home into ~/.gitconfig > --site into /etc/gitconfig > --share into /usr/share/git/config
BTW, if we go that far, maybe it makes more sense to implement a way to include files other config files? So repo-level config can (maybe implicitely) have an "include ~/.gitconfig" which in turn can "include /etc/gitconfig".
We could even do like C-preprocessor does: relative pathnames can be searched in a defined set of directores.
That's all overengineered, probably. I never needed .git/config, except for switching exec-bit (which I'd like to have on per-site basis, to be fair).