From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: jn/config-ignore-inaccessible (Re: What's cooking in git.git (Apr 2013, #10; Mon, 29))
Date: Sat, 4 May 2013 13:14:14 -0700 [thread overview]
Message-ID: <20130504201414.GA2420@elie.Belkin> (raw)
In-Reply-To: <87y5bvyw7j.fsf@hexa.v.cablecom.net>
Thomas Rast wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>> * jn/config-ignore-inaccessible (2013-04-15) 1 commit
>> - config: allow inaccessible configuration under $HOME
>>
>> When $HOME is misconfigured to point at an unreadable directory, we
>> used to complain and die. This loosens the check.
>>
>> I do not think we agreed that this is a good idea, though.
>
> As a data point: yesterday on IRC, two users complained that they each
> had this problem.
>
> http://colabti.org/irclogger/irclogger_log/git?date=2013-05-03#l3022
> http://colabti.org/irclogger/irclogger_log/git?date=2013-05-03#l3111
I think the approach taken in the patch above is a good one. If
/etc/gitconfig contains important configuration, it is still not
ignored, errors other than permissions reading ~/.gitconfig are
still fatal, and permissions errors accessing ~/.gitconfig are no
longer fatal because they are expected as something very common
in normal setups.
I haven't been able to convince myself there is a different, better
behavior to be found. Special-casing inaccessible $HOME while still
forbidding inaccessible $HOME/.config/git and $HOME/.gitconfig would
seem strange.
Hmm?
Jonathan
next prev parent reply other threads:[~2013-05-04 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 21:01 What's cooking in git.git (Apr 2013, #10; Mon, 29) Junio C Hamano
2013-05-01 1:48 ` Felipe Contreras
2013-05-04 8:40 ` Thomas Rast
2013-05-04 19:27 ` Junio C Hamano
2013-05-04 20:14 ` Jonathan Nieder [this message]
2013-05-05 3:55 ` jn/config-ignore-inaccessible (Re: What's cooking in git.git (Apr 2013, #10; Mon, 29)) Junio C Hamano
2013-05-07 18:41 ` Jeff King
2013-05-06 9:54 ` Thomas Rast
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=20130504201414.GA2420@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=trast@inf.ethz.ch \
/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).