From: Nathan Neulinger <nneul@neulinger.org>
To: git@vger.kernel.org
Subject: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig
Date: Fri, 30 May 2014 13:19:17 -0500 [thread overview]
Message-ID: <5388CBA5.9030403@neulinger.org> (raw)
Four related feature requests/ideas:
1. equivalent to GIT_*_EMAIL/NAME vars, but processed only if git config doesn't set values
Right now, there isn't any way to have a systemwide profile script that tries to determine a better default for the user
name/email values, such as in the case of shared logins. The best I've been able to do for now is use the 'EMAIL' var.
Use case in my environment - most shared-login accounts are accessed via krb5 login, so it provides a nice way to set a
better default for "who is doing this commit" than just the userid.
2. Setting option to user.name (or other setting) that would BLOCK the commit from occurring at all if it would
otherwise fall back to defaults. I thought this previously worked by setting an empty value, but apparently doesn't work
that way in current versions.
3. Setting option to user.name/user.email to prompt, SVN-style, for the name/email. Yes, this would be
annoying/obnoxious to use normally, but intent is to avoid un-named "root@host" commits that would otherwise occur from
user being lazy.
4. (This would accomplish all of the above) - enhance the include.path option to support the "!" syntax similar to what
aliases can do. i.e.
[include]
path = !/usr/local/bin/gen-git-env
or
[include]
cmd = /usr/local/bin/gen-git-env
-- Nathan
------------------------------------------------------------
Nathan Neulinger nneul@neulinger.org
Neulinger Consulting (573) 612-1412
next reply other threads:[~2014-05-30 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 18:19 Nathan Neulinger [this message]
2014-05-30 18:27 ` feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig 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
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=5388CBA5.9030403@neulinger.org \
--to=nneul@neulinger.org \
--cc=git@vger.kernel.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).