FWIW, the issue is still present. ---------- Forwarded message ---------- From: Alex Riesen <raa.lkml@xxxxxxxxx> 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@xxxxxxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html