From: Johannes Sixt <johannes.sixt@telecom.at>
Date: Sun, 30 Sep 2007 21:34:36 GMT
Subject: Re: [PATCH 0/5] fork/exec removal series
Message-ID: <200709302334.37129.johannes.sixt@telecom.at>
In-Reply-To: <Pine.LNX.4.64.0709302212160.28395@racer.site>

On Sunday 30 September 2007 23:14, Johannes Schindelin wrote:
> On Sun, 30 Sep 2007, Johannes Sixt wrote:
> > - The fork()s are not followed by exec(). These need a different
> >   implementation. I am thinking of a start_coroutine()/finish_coroutine()
> >   API that is implemented with threads in MinGW. (Suggestions of a better
> >   as well as implementations are welcome.)
>
> Is there more than the case I introduced with shallow clones?

I don't know which one you are refering to.

These cases I hope to be able to treat as "coroutine":

- sideband demultiplexer in builtin-fetch-pack.c
- internal rev-list in upload-pack
- the two-way pipe handling in convert.c and builtin-upload-archive.c

There are probably more in daemon.c and imap-send.c.

BTW, the convert.c case (apply_filter) is most interesting for me, since I 
have a real-world use-case for a clean-filter.

-- Hannes