git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Kraai <kraai@ftbfs.org>
To: Mike Gorchak <mike.gorchak.qnx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Improve QNX support in GIT
Date: Tue, 26 Feb 2013 13:02:46 -0800	[thread overview]
Message-ID: <20130226210246.GB3502@ftbfs.org> (raw)
In-Reply-To: <CAHXAxrOcC7GX-rhT793t4vcF68TvrE9w9OW856+7cGDBGMx0VA@mail.gmail.com>

On Tue, Feb 26, 2013 at 10:32:16PM +0200, Mike Gorchak wrote:
> I see. Most resource managers use procmgr_daemon(), which has no such
> limitation. Anyway, as far as I can see current git sources do not use
> fork together with pthread, except for daemonize() function.

If threads are enabled, git does use fork after calling pthread_create:

 * When I run "git grep foo".
 * When I run "git fetch" to update my git working copy, which is
   using an HTTPS remote.

Both of these commands fail as a result.

  parent reply	other threads:[~2013-02-26 21:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 20:13 [PATCH] Improve QNX support in GIT Matt Kraai
2013-02-26 20:32 ` Mike Gorchak
2013-02-26 20:53   ` Johannes Sixt
2013-02-26 21:02   ` Matt Kraai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-26 17:25 Matt Kraai
2013-02-26 18:09 ` David Michael
2013-02-26 18:36 ` Mike Gorchak
2013-02-26 18:54 ` Mike Gorchak
2013-02-23 22:02 Mike Gorchak
2013-02-24  7:36 ` Mike Gorchak
2013-02-24  8:46   ` Junio C Hamano
2013-02-24 14:12     ` Mike Gorchak
2013-02-24 21:24       ` Junio C Hamano
2013-02-25  7:14         ` Junio C Hamano
2013-02-25  8:30           ` Mike Gorchak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130226210246.GB3502@ftbfs.org \
    --to=kraai@ftbfs.org \
    --cc=git@vger.kernel.org \
    --cc=mike.gorchak.qnx@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).