thanks for your reply on my issue.
Here are the following outputs you asked for:
git version 2.7.4 (Apple Git-66)
I have tried the Homebrew version of git, but no change in case of the issue.
I just customized my system with the Mathias Bynens dotfiles
(https://github.com/mathiasbynens/dotfiles) as well as with drduhs OS X
Security Guide (https://github.com/drduh/OS-X-Security-and-Privacy-Guide).
Because I reinstall my Mac on a regularly basis, wherefore I can say that one
year ago these tweaks have not caused any issue.
Thanks a lot. I really appreciate your help.
> Gesendet: Dienstag, 20. September 2016 um 13:02 Uhr
> Von: "Heiko Voigt" <hvo...@hvoigt.net>
> An: "Jonas Thiel" <jonas.liersch...@gmx.de>
> Cc: firstname.lastname@example.org
> Betreff: Re: Homebrew and Git
> On Sun, Sep 18, 2016 at 05:50:28PM +0200, Jonas Thiel wrote:
> > A while ago I have described my problem with Homebrew at the following
> > GitHub channel
> > (https://github.com/Homebrew/homebrew-core/issues/2970). In the
> > meanwhile, I believe that I my problem with Homebrew is based on an
> > issues with my Git. I have found the attached Git Crash reports on my
> > Mac and because I am not familiar with reading/analysing Crash
> > Reports, it would be great if someone could give me some feedback on
> > it.
> > If you have any question, please do not hesitate to contact me.
> From your crash reports I see that git is apparently crashing in a
> strchr() call from within ident_default_email() which is a function that
> tries to assemble a name and email to put into your commits.
> Can you post us the output of
> hostname -f
> Since it seems you are using an Apple git can you also give us the
> output of
> git version
> Since it seems that Apple is compiling its own git (and not publishing
> the changes they made conveniently via git). Have you tried
> installing a vanilla git via homebrew and seeing whether that also
> produces the issue?
> In your bugreport you are talking about modifications you do to your
> system after which the issue occurred. I would suggest to exactly find
> out which step lead to git crashing (if it actually is the issue). First
> to identify an issue we need something that is reproduceable.
> Cheers Heiko