From: Alex Riesen <raa.lkml@gmail.com>
Date: Sat, 28 Dec 2013 14:56:55 GMT
Subject: Fwd: Runaway "git remote" if group definition contains a remote by the same name
Message-ID: <CALxABCbRZ4MmiYS4JF20qf1-iubeTfa+3OLibqdb5+raekuKQg@mail.gmail.com>
In-Reply-To: <AANLkTinni=VJLoZp1Hjm4dfW8faChytDObJbXsFF5iXv@mail.gmail.com>

FWIW, the issue is still present.

---------- Forwarded message ----------
From: Alex Riesen <raa.lkml@gmail.com>
Date: Wed, Nov 17, 2010 at 6:10 PM
Subject: Runaway "git remote" if group definition contains a remote by
the same name
To: Git Mailing List <git@vger.kernel.org>


Hi,

it is also a way to create a fork bomb out of the innocent tool on platforms
where pressing Ctrl-C does not terminate subprocesses of the foreground
process (like, of course, Windows).

To reproduce, run

   git -c remotes.origin='origin other' remote update origin

I just cannot look at it right now, and have to resolve to only reporting
the problem to warn people. Something seems to resolve the remotes group
definition over and over again.