git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

From
Nathan Neulinger <nneul@neulinger.org>
Date
May 30, 2014, 18:44 UTC
Message-ID
<5388D175.3060500@neulinger.org>
In-Reply-To
<20140530182746.GK12314@google.com>
> I wouldn't mind having a GIT_EMAIL envvar with the semantics you mean,
> but can you say more about the use case?  What's wrong with the usual
> EMAIL environment variable?

EMAIL actually worked for this case for me, but there wasn't any equivalent for author name, so the commits all look like "sharedaccount <myuser@mydomain>".

Show 7 quoted lines
> [...]
>> [include]
>>     path = !/usr/local/bin/gen-git-env
>
> This is scary in terms of privilege escalation attacks.  ("Admin,
> could you please take a look at this repo?  When I run 'git status',
> ...".)

Wouldn't that be pulling from ~sharedaccount/.gitconfig anyway though? (Agreed that it could be an issue if you have shared ssh agent, krb5 tgts, etc. - but that would exist any time you connected into a shared account.)

I would probably take the approach of not supporting that syntax in anything other than the per-user gitconfig file though as a safety measure - per-repo config could indeed be a problem.

-- Nathan

------------------------------------------------------------ Nathan Neulinger nneul@neulinger.org Neulinger Consulting (573) 612-1412

Previous: Jonathan NiederNext: Junio C Hamano
Message 3 of 8 in “feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig”
  1. Nathan NeulingerMay 30, 2014
  2. Jonathan NiederMay 30, 2014
  3. Nathan NeulingerMay 30, 2014
  4. Junio C HamanoMay 30, 2014
  5. Nathan NeulingerMay 30, 2014
  6. Jeff KingMay 30, 2014
  7. Junio C HamanoMay 30, 2014
  8. Jeff KingJun 2, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.