From: Eric Blake <eblake@redhat.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Matthias Lederhofer" <matled@gmx.net>,
"Jürgen Rühle" <j-r@online.de>
Subject: Re: Fix 'git log' early pager startup error case
Date: Wed, 25 Aug 2010 08:22:49 -0600 [thread overview]
Message-ID: <4C752739.3010808@redhat.com> (raw)
In-Reply-To: <4C74BFA7.1090907@viscovery.net>
On 08/25/2010 01:00 AM, Johannes Sixt wrote:
> Am 8/25/2010 3:36, schrieb Jonathan Nieder:
>> Mingw Git uses spawnvpe now, but Cygwin users might still suffer from
>> fork() troubles. I think it should be possible to work around that by
>> using posix_spawn() from start_command() on such platforms (or
>> someting similar).
>
> Just FYI, posix_spawn() is not sufficiently capable for the demands of
> start_command(): It doesn't allow to set a new CWD for the spawned process.
And even if posix_spawn() were capable, cygwin doesn't yet implement it.
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
next prev parent reply other threads:[~2010-08-25 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 17:33 Fix 'git log' early pager startup error case Linus Torvalds
2010-08-25 1:36 ` Jonathan Nieder
2010-08-25 7:00 ` Johannes Sixt
2010-08-25 14:22 ` Eric Blake [this message]
2010-08-26 6:18 ` setting working dir in posix_spawn() (Re: Fix 'git log' early pager startup error case) Jonathan Nieder
2010-08-26 7:16 ` Joshua Juran
2010-08-26 14:13 ` Eric Blake
2010-08-25 19:16 ` Fix 'git log' early pager startup error case Junio C Hamano
2010-08-25 20:05 ` Linus Torvalds
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=4C752739.3010808@redhat.com \
--to=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j-r@online.de \
--cc=j.sixt@viscovery.net \
--cc=jrnieder@gmail.com \
--cc=matled@gmx.net \
--cc=torvalds@linux-foundation.org \
/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).