> I don't think it's a good idea to just enable thread support. On QNX,
> once a process creates a thread, fork stops working. This breaks
> commands that create threads and then try to run other programs, such
> as "git fetch" with an https remote. If threads are enabled, I think
> that the uses of fork need to be audited and, if they can be called
> after a thread is created, fixed.
I did a quick look into the run-command.c and transport-helper.c
modules, they use pthread OR fork for external command spawning
depending on NO_PTHREAD declaration. Another fork() occurence in the
module daemon.c for daemonization and I know that it works.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html