On 1/18/07, Shawn O. Pearce <spearce@spearce.org> wrote: > > don't think so. I _would_ cry seeing how fork(2) gets ported to Windows, > > and you will, probably... after seeing how it is done in cygwin. > > AFAIK there's not a strong reason to keep fork() in Git. > > Currently anytime we fork a process its to perform a small amount > of file descriptor redirection and then immediately exec some other > executable, or a hook script. In other words we probably could > convert all current uses of fork to something like in run-command.c, > which a Windows port could then easily replace using CreateProcess(). I count 17 instances (excluding run_command). At least fetch-pack is not trivial (the sideband code. Could be done in a thread, which is not portable just as well). > But removing fork isn't worth doing until someone is seriously > trying to port Git onto Windows without Cygwin. The current code > works on sane OSes and isn't broken, so why fix it? Right. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Jan 19 02:53:31 2007
This archive was generated by hypermail 2.1.8 : 2007-01-19 02:55:44 EST