Thomas Rast wrote:
> Junio C Hamano <gits...@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.
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
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html