From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Hilco Wijbenga <hilco.wijbenga@gmail.com>,
nguyenhu@minatec.inpg.fr, git@vger.kernel.org,
matthieu.moy@grenoble-inp.fr,
Valentin DUPERRAY <Valentin.Duperray@phelma.grenoble-inp.fr>,
Franck JONAS <Franck.Jonas@phelma.grenoble-inp.fr>,
Lucien KONG <Lucien.Kong@phelma.grenoble-inp.fr>,
Thomas NGUY <Thomas.Nguy@phelma.grenoble-inp.fr>,
Huynh Khoi Nguyen NGUYEN
<Huynh-Khoi-Nguyen.Nguyen@phelma.grenoble-inp.fr>
Subject: Re: [RFC] Possibility to choose ~/.config/git/config instead of ~/.gitconfig
Date: Fri, 25 May 2012 13:44:09 -0500 [thread overview]
Message-ID: <20120525184408.GA4740@burratino> (raw)
In-Reply-To: <7vsjeortwu.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>> If I understand correctly, the proposal that started this thread was
>> to give people a chance to tidy their HOME directory by moving
>> personal git configuration under ~/.config/git/.
>
> So it is exactly "I do not want ~/.gitconfig, I want ~/.config/git", no?
>
> That is something distro should be able to decide.
Except that there is nothing distro-specific about it. Do you really
want the config file to have a different name depending on whether one
is using Debian, Fedora, Mac OS X, Gentoo, one of the various builds of
git on Windows, Solaris, ...?
Besides, with my distro package maintainer hat on, I can tell you that
switching the config file to ~/.config/git and not reading
~/.gitconfig would be a complete nonstarter. That would mean that the
existing user configuration for everyone would just seem to disappear.
Once the code to read both files is written, why would one want that
to be distro-specific and not something shared?
Hoping that clarifies a little,
Jonathan
next prev parent reply other threads:[~2012-05-25 18:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 16:15 [RFC] Possibility to choose ~/.config/git/config instead of ~/.gitconfig nguyenhu
2012-05-25 17:01 ` Jonathan Nieder
2012-05-25 17:29 ` Matthieu Moy
2012-05-25 17:44 ` Jonathan Nieder
2012-05-25 17:31 ` Hilco Wijbenga
2012-05-25 17:42 ` Jonathan Nieder
2012-05-25 17:47 ` Hilco Wijbenga
2012-05-25 18:12 ` [PATCH] config doc: remove confusion about relative GIT_DIR from FILES section Jonathan Nieder
2012-05-25 20:06 ` Jeff King
2012-05-25 18:20 ` [RFC] Possibility to choose ~/.config/git/config instead of ~/.gitconfig Junio C Hamano
2012-05-25 17:54 ` Matthieu Moy
2012-05-25 20:11 ` Jeff King
2012-05-25 18:13 ` Junio C Hamano
2012-05-25 18:25 ` Jonathan Nieder
2012-05-25 18:34 ` Junio C Hamano
2012-05-25 18:44 ` Jonathan Nieder [this message]
2012-05-25 18:58 ` Junio C Hamano
2012-05-25 19:13 ` Matthieu Moy
2012-05-25 19:17 ` Jonathan Nieder
2012-05-25 19:29 ` Matthieu Moy
2012-05-25 19:35 ` Jonathan Nieder
2012-05-25 19:37 ` Jonathan Nieder
2012-05-25 19:39 ` Matthieu Moy
2012-05-25 19:01 ` Matthieu Moy
2012-05-26 10:45 ` Felipe Contreras
2012-05-26 10:59 ` Heiko Voigt
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=20120525184408.GA4740@burratino \
--to=jrnieder@gmail.com \
--cc=Franck.Jonas@phelma.grenoble-inp.fr \
--cc=Huynh-Khoi-Nguyen.Nguyen@phelma.grenoble-inp.fr \
--cc=Lucien.Kong@phelma.grenoble-inp.fr \
--cc=Thomas.Nguy@phelma.grenoble-inp.fr \
--cc=Valentin.Duperray@phelma.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hilco.wijbenga@gmail.com \
--cc=matthieu.moy@grenoble-inp.fr \
--cc=nguyenhu@minatec.inpg.fr \
/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).