Your message dated Sun, 16 Dec 2018 13:46:56 -0800 with message-id <[email protected]> and subject line Re: git push: segfault for non-forced non-ff push of other branch from unborn branch has caused the Debian Bug report #705308, regarding git push: segfault for non-forced non-ff push of other branch from unborn branch to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 705308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705308 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: git Version: 1:1.7.10.2-1 Tags: upstream patch Control: fixed -1 1:1.8.2-1 Hi, v1.7.10.2~2^2~2 (push: Provide situational hints for non-fast-forward errors, 2012-03-20) introduced a segfault: After a push of a branch other than the current branch fails in a no-ff error and if you are still on an unborn branch, the code recently added to report the failure dereferences a null pointer while checking the name of the current branch. v1.8.1.3~4^2 (push: fix segfault when HEAD points nowhere, 2013-01-31) fixes it.
--- End Message ---
--- Begin Message ---This is fixed in stable and oldstable, so marking done. Please don't hesitate to write if it happens again.
--- End Message ---
