On Mon, Dec 30, 2013 at 11:10:31AM -0800, Junio C Hamano wrote:
> > So I think the sanest thing is probably:
> >
> > 1. Teach "fetch" to expand recursively in a single process, and then
> > tell sub-processes (via a new command-line option) not to expand
> > any further.
> >
> > 2. T
Jeff King writes:
> If they are not allowed to recurse, the problem is much easier; the
> parent fetch simply tells all of the sub-invocations not to expand the
> arguments further. However, whether it was planned or not, it has been
> this way for a long time. I would not be surprised if somebod
On Sat, Dec 28, 2013 at 03:56:55PM +0100, Alex Riesen wrote:
> 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.
FWIW, the issue is still present.
-- Forwarded message --
From: Alex Riesen
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
Hi,
it is also a way to create a fork bomb out of the innoce
4 matches
Mail list logo
