After a recent 'cleanup' operation that attempted to simplify my
GPG key workflow with Yubikeys, it looks like my GPG installation
has 'forgotten' how to interact with the key I typically used
to sign GitPython releases.

Since I never managed to establish a chain of trust with my only
remaining 'good' key, for you this means you cannot trust new
GitPython releases anymore.

There is nothing I can do about except to apologize for the hassle.

If you want to make constructive suggestions on how to fix this, I am
happy to work with you on that.

It's possible to specify a pathspec (eg :!foo) to git diff/status/...
but it currently fails with:

git.exc.GitCommandError: Cmd('/usr/bin/git') failed due to: exit code(128)
  cmdline: /usr/bin/git diff --abbrev=40 --full-index --raw :!foo
  stderr: 'fatal: ambiguous argument ':!foo': unknown revision or path not in the working tree.

Add missing '--' to the arguments to fix this ambiguity

Signed-off-by: Arnaud Patard <[email protected]>

Calling getpass.getuser may lead to breakage in environments where there
is no entries in the /etc/passwd file for the current user.

Setting the environment variables for the git user configurations should
prevents GitPython from using values from /etc/passwd. However, doing so
will not prevent reading /etc/passwd and looking for an entry with the
current user UID.

This patch changes the behavior described above so GitPython will
perform a lazy evaluation of /etc/passwd, only doing so when the
environment variables for the git user configuration are not available.

Signed-off-by: Athos Ribeiro <[email protected]>

In c96476b, the new default_name nested function does not contain a
retun statement. This leads to an issue when the environment variables
are not present, where the actor name would not be set.

Signed-off-by: Athos Ribeiro <[email protected]>