Hi, I noticed that "git stash" creates commits with this author and committer:

    git stash <git@stash>

This domain does not currently exist, but
someone could buy it from ICANN for about US$10,000 (I think).
That could cause exciting and weird bugs, such as
third-party scripts accidentally emailing classified changes to git@stash.

Please use a different domain that is either

  1) controlled by someone trustworthy (e.g. git/SFC, or Debian/SPI)
  2) is guaranteed (by RFCs) to fail

For comparison:

 * "canon" is an example gTLD owned by a company.

 * "ai" is an example ccTLD with working mail,
    i.e. <abuse@ai> is valid email address.

 * "invalid" is required to not work on the internet by some RFC (FIXME: which one?)

 * "example.com" apparently has an MX that deliberately doesn't work?
   I'm not sure if that is *guaranteed*, though.

Steps to reproduce:

    bash5$ git init
    Initialized empty Git repository in /tmp/with-temp-dir.XHK2wf/.git/
    bash5$ date >x
    bash5$ git add x
    bash5$ git commit -amx
    [master (root-commit) fe27c16] x
     1 file changed, 1 insertion(+)
     create mode 100644 x
    bash5$ date >x
    bash5$ git stash
    Saved working directory and index state WIP on master: fe27c16 x
    bash5$ git log --format=$'%aN <%aE>\n%cN <%cE>'
    Trent W. Buck <trentbuck@gmail.com>
    Trent W. Buck <trentbuck@gmail.com>
    bash5$ git log --all --format=$'%aN <%aE>\n%cN <%cE>'
    git stash <git@stash>
    git stash <git@stash>
    git stash <git@stash>
    git stash <git@stash>
    Trent W. Buck <trentbuck@gmail.com>
    Trent W. Buck <trentbuck@gmail.com>