threads / discuss / 29168

Suppressing the user.name warning

Subject: Suppressing the user.name warning

## tl;dr

2 messages between Dec 14, 2011 and Dec 14, 2011.

replies: 1people: 2as markdown or json

Jay Levitt· Dec 14, 2011, 21:50 UTC · lore

Is there a way to suppress the user.name/email warning without configuring them in .gitconfig? I want to pass them in SSH as GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL; git uses the values, but still warns me every time.

Seems like if git can get that data in any form, it shouldn't complain about not having it. No?

Jay Levitt
Jeff King· Dec 14, 2011, 22:16 UTC · re: Jay Levitt · lore

Re: Suppressing the user.name warning

On Wed, Dec 14, 2011 at 04:50:21PM -0500, Jay Levitt wrote:
Show 7 quoted lines
> Is there a way to suppress the user.name/email warning without
> configuring them in .gitconfig? I want to pass them in SSH as
> GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL; git uses the values, but still
> warns me every time.
> 
> Seems like if git can get that data in any form, it shouldn't
> complain about not having it.  No?

Git should not be complaining if it gets the data from the environment. However, you should also be setting GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL. Otherwise they will come from the passwd file, and git will issue the warning.

-Peff

← back to recent threads