From: Josh Triplett <josh@freedesktop.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Only use ETC_GITCONFIG=$(prefix)/etc/gitconfig ifeq ($(prefix),$(HOME))
Date: Mon, 23 Apr 2007 22:44:24 -0700 [thread overview]
Message-ID: <462D9938.8020206@freedesktop.org> (raw)
In-Reply-To: <7vhcr6bdmk.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Junio C Hamano wrote:
> Is this really necessary?
>
> I personally think distro people (or anybody who configures git
> for system-wide deployment for that matter) already has Makefile
> wrapper (a la debian/rules) to take care of this and other
> issues.
So did I. Then I noticed (while stracing git to diagnose the issue with
git-add searching the whole working copy for .gitignore files) that the
Debian-packaged git looked for /usr/etc/gitconfig. See
<http://bugs.debian.org/420675>. Apparently few enough people use
/etc/gitconfig that nobody noticed and reported that it didn't work. :)
Why not make the defaults more resistant to broken configuration?
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-04-24 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 2:11 [PATCH] Only use ETC_GITCONFIG=$(prefix)/etc/gitconfig ifeq ($(prefix),$(HOME)) Josh Triplett
2007-04-24 4:27 ` Junio C Hamano
2007-04-24 5:44 ` Josh Triplett [this message]
2007-04-24 5:59 ` Junio C Hamano
2007-04-24 7:23 ` Josh Triplett
2007-04-24 7:51 ` [PATCH] Create a sysconfdir variable, and use it for ETC_GITCONFIG Josh Triplett
2007-04-24 8:12 ` Junio C Hamano
2007-04-24 6:08 ` [PATCH] Only use ETC_GITCONFIG=$(prefix)/etc/gitconfig ifeq ($(prefix),$(HOME)) Junio C Hamano
2007-04-24 6:17 ` Junio C Hamano
2007-04-24 9:05 ` Sergio Callegari
2007-04-24 6:19 ` Shawn O. Pearce
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=462D9938.8020206@freedesktop.org \
--to=josh@freedesktop.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.