From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 5/8] Teach run_command how to setup a stdin pipe
Date: Sat, 10 Mar 2007 20:45:33 -0500 [thread overview]
Message-ID: <20070311014533.GA10343@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0703101753440.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Sat, 10 Mar 2007, Shawn O. Pearce wrote:
>
> > Sometimes callers trying to use run_command to execute a child process
> > will want to setup a pipe or file descriptor to redirect into the
> > child's stdin.
> >
> > This idea is completely stolen from builtin-bundle's fork_with_pipe,
> > written by Johannes Schindelin. All credit (and blame) should lie with
> > Dscho. ;-)
>
> ;-)
>
> Thank you for starting this thread. I think it makes a lot of sense in the
> face of the MinGW port. (I am not interested in the hook stuff personally,
> so I'll not comment on that.)
I'd like to see run_command learn how to also redirect stdout,
then replace fork_with_pipe in builtin-bundle with run_command.
We should be able to also improve some of our other more direct
uses of fork to use run_command at that point too.
I don't know squat about MinGW, so I don't know if having the
run_command abstraction really helps there or not, but I know we
tried to make it with the good intentions of being able to use it
to wrap that asinine CreateProcess() thing that Win32 has...
--
Shawn.
next prev parent reply other threads:[~2007-03-11 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 8:28 [PATCH 5/8] Teach run_command how to setup a stdin pipe Shawn O. Pearce
2007-03-10 16:54 ` Johannes Schindelin
2007-03-11 1:45 ` Shawn O. Pearce [this message]
2007-03-11 2:07 ` Johannes Schindelin
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=20070311014533.GA10343@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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