Hi Greg,

Greg Price wrote:
> On Wed, Apr 29, 2020 at 12:49 AM Greg Price <[email protected]> wrote:
> > I tried reproducing this on the Git 2.20 in buster (with the
> > reproduction recipe from message #14), and it seems it
> > has been fixed! Same with the Git 2.26 backported from bullseye.
> >
> > Instead of a fork bomb, there's an error message:
> 
> I did a bit more testing, this time with containers running stretch
> and jessie. The bug reproduces in jessie -- no surprise, given the
> original report. But as of stretch, which at this point is oldstable,
> it seems to already be fixed. So I believe the bug can be closed.

Thanks for checking and closing.

Haven't run into it again either. (Didn't try to provoke it though
neither.)

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <[email protected]>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Reply via email to