From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nathan Neulinger <nneul@neulinger.org>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org
Subject: Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig
Date: Mon, 2 Jun 2014 02:59:51 -0400 [thread overview]
Message-ID: <20140602065947.GC27254@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq1tvb7xw6.fsf@gitster.dls.corp.google.com>
On Fri, May 30, 2014 at 02:35:37PM -0700, Junio C Hamano wrote:
> Nathan's installation can set a "GIT_MYSELF" and then have something
> like this in the shared $HOME/.gitconfig
>
> [include]
> path = /usr/local/users/$GIT_MYSELF/ident
>
> we could even make the whole thing fail when GIT_MYSELF is not set
> but I haven't thought things through ;-)
Yeah, that is something I considered[1] when writing the initial
include.path implementation. Something like:
[include]
path = .gitconfig-$HOSTNAME
could be potentially useful. But I punted at the time to wait for
somebody to actually ask for it. If somebody wanted to implement it, I
don't see a reason to avoid it.
-Peff
[1] http://article.gmane.org/gmane.comp.version-control.git/190196
prev parent reply other threads:[~2014-06-02 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 18:19 feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig Nathan Neulinger
2014-05-30 18:27 ` Jonathan Nieder
2014-05-30 18:44 ` Nathan Neulinger
2014-05-30 19:48 ` Junio C Hamano
2014-05-30 19:58 ` Nathan Neulinger
2014-05-30 20:09 ` Jeff King
2014-05-30 21:35 ` Junio C Hamano
2014-06-02 6:59 ` Jeff King [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=20140602065947.GC27254@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=nneul@neulinger.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).