From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Frank Lichtenheld" <frank@lichtenheld.de>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] gitweb: Use list form of 'open "-|"' pipeline
Date: Tue, 11 Mar 2008 22:09:03 -0400 [thread overview]
Message-ID: <76718490803111909p9684463j355c1f587bf31b13@mail.gmail.com> (raw)
In-Reply-To: <20080311185916.GO10103@mail-vs.djpig.de>
On Tue, Mar 11, 2008 at 2:59 PM, Frank Lichtenheld <frank@lichtenheld.de> wrote:
> After taking a look at the IPC::Run code myself I'm not really sure it
> is really "worthwile", as I put it, to try to understand that.
>
> Creating a less flexible solution that is readable might be better.
"man perlipc" - search for "Safe Pipe Opens".
j.
prev parent reply other threads:[~2008-03-12 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 16:57 [RFC/PATCH] gitweb: Use list form of 'open "-|"' pipeline Jakub Narebski
2008-03-08 17:51 ` Charles Bailey
2008-03-08 18:29 ` Jakub Narebski
2008-03-11 9:01 ` Frank Lichtenheld
2008-03-11 17:30 ` Jakub Narebski
2008-03-11 18:59 ` Frank Lichtenheld
2008-03-12 2:09 ` Jay Soffian [this message]
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=76718490803111909p9684463j355c1f587bf31b13@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=jnareb@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).