From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: /etc/gitconfig
Date: Wed, 14 Feb 2007 11:40:52 +0100 [thread overview]
Message-ID: <20070214104052.GA9047@informatik.uni-freiburg.de> (raw)
In-Reply-To: <200702140909.28369.andyparkins@gmail.com>
Andy Parkins wrote:
> With the release of 1.5.0 I added legacyheaders=false and
> usedelatbaseoffset=true to my repositories.
>
> While doing that though, it felt wrong to be editing every single config. Is
> there a justification for having three config files?
>
> /etc/gitconfig
> $HOME/.gitconfig
> $GIT_DIR/config
>
> With /etc/gitconfig coming in at lowest priority?
I didn't try it, but maybe you could place your desired config to
/usr/share/git-core/templates/config and then at least newly created
repos get it?
Best regards
Uwe
--
Uwe Kleine-König
$ dc -e "5735816763073014741799356604682P"
prev parent reply other threads:[~2007-02-14 10:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 9:09 /etc/gitconfig Andy Parkins
2007-02-14 10:30 ` /etc/gitconfig Peter Baumann
2007-02-14 11:48 ` [PATCH] config: read system-wide defaults from /etc/gitconfig Johannes Schindelin
2007-02-14 16:30 ` Junio C Hamano
2007-02-14 17:45 ` Johannes Schindelin
2007-02-14 17:57 ` Junio C Hamano
2007-02-14 18:02 ` Johannes Schindelin
2007-02-14 18:12 ` Junio C Hamano
2007-02-14 18:19 ` Nicolas Pitre
2007-02-14 19:06 ` Junio C Hamano
2007-02-15 10:19 ` Andy Parkins
2007-02-15 11:26 ` Junio C Hamano
[not found] ` <20070215113557.GB2282@steel.home>
[not found] ` <20070216143952.GA2478@steel.home>
2007-02-16 14:42 ` [PATCH] Allow config files to be included Alex Riesen
2007-02-16 14:45 ` Alex Riesen
2007-02-14 18:10 ` [PATCH] config: read system-wide defaults from /etc/gitconfig Han-Wen Nienhuys
2007-02-14 19:07 ` Junio C Hamano
2007-02-14 19:25 ` Johannes Schindelin
2007-02-14 19:43 ` Junio C Hamano
2007-02-14 19:54 ` Johannes Schindelin
2007-02-14 22:39 ` Johannes Schindelin
2007-02-15 5:27 ` Junio C Hamano
2007-02-15 8:46 ` Junio C Hamano
2007-02-15 9:59 ` Eric Wong
2007-02-15 10:03 ` Eric Wong
2007-02-15 10:36 ` Junio C Hamano
2007-02-15 10:43 ` Johannes Schindelin
2007-02-15 11:25 ` Junio C Hamano
2007-02-15 12:05 ` Johannes Schindelin
2007-02-19 1:47 ` Jakub Narebski
2007-02-14 10:40 ` Uwe Kleine-König [this message]
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=20070214104052.GA9047@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--cc=andyparkins@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.
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).