What's the status of this upstream?

What's the status of this upstream?

Here's message with patch from zsh dev: http://www.zsh.org/mla/workers/2019/msg00058.html

It seems they've noticed the bug too late. Probably will be fixed in the next release

Is there a reason this patch is necessary in nixpkgs? What differentiates this from every other bug in zsh whose fixes aren't released yet?

• It causes error or segfault in popular configurations
• It has also been applied in other distributions, or at least Debian.

Question seems a bit unfair? I mean presumably this fix is at least motivated by impacting the submitting user. While yes we don't chase every commit I don't think we're so release-only that we leave breakage with known upstream fixes?

FWIW this was also fixed almost immediately after 5.7 was posted. I'd be running with this patch myself if I didn't kludge around the issue in my config already :).

Alright, sorry didn't want it to sound like that. This problem seemed pretty non-fatal to me (because I thought it would only occur if you ran a git specific command outside of a git repo), but I think I get it now that this error happens all the time, which then sounds more reasonable to fix.