All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
	"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>,
	austin-group-futures-l@opengroup.org
Subject: Re: setting working dir in posix_spawn() (Re: Fix 'git log' early pager startup error case)
Date: Thu, 26 Aug 2010 08:13:22 -0600	[thread overview]
Message-ID: <4C767682.7030700@redhat.com> (raw)
In-Reply-To: <20100826061815.GH9708@burratino>

On 08/26/2010 12:18 AM, Jonathan Nieder wrote:
> Do you think there would be any interest in a posix_spawn() variant
> that takes a dir parameter?  I am imagining something like this:

Of your variants, I would most prefer:

>   int posix_spawn_file_actions_addchdir(posix_spawn_file_actions_t
> 	*file_actions, int dirfd);

For that matter, it may also be worth adding 
posix_spawn_file_actions_addopenat, which mirrors the recent addition of 
openat() semantics.

-- 
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

  parent reply	other threads:[~2010-08-26 14:16 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
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 [this message]
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=4C767682.7030700@redhat.com \
    --to=eblake@redhat.com \
    --cc=austin-group-futures-l@opengroup.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.