From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Introduce git version --list-features for porcelain use
Date: Fri, 01 Jun 2007 09:13:57 +0200 [thread overview]
Message-ID: <465FC735.C78ACD5@eudaptics.com> (raw)
In-Reply-To: 20070601030959.GY7044@spearce.org
"Shawn O. Pearce" wrote:
> Why cat? Tcl is so horribly broken that to get data for both stdout
> and stderr through a pipe I have to do something sick like:
>
> git fetch 2>&1 | cat
>
> because in Tcl its actually:
>
> set rdr [open "| git fetch |& cat" r]
>
> The |& means 2>&1| in normal shell. But that means I have to have
> a process after it to receive the data. Normally that's cat.
> But MinGW doesn't have cat. (Nor do they have dog, but neither
> does Linux...). So I need a way to redirect output.
Are you planning for the future? Currently, the MinGW port works only
with MSYS installed and $MSYS/bin in your PATH because the shell scripts
need an assorted set of POSIX tools. MSYS does ship 'cat', of course.
-- Hannes
next prev parent reply other threads:[~2007-06-01 7:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:31 [PATCH] Introduce git-supported-features for porcelain use Shawn O. Pearce
2007-05-30 12:04 ` Alex Riesen
2007-05-30 12:34 ` Johannes Schindelin
2007-05-31 0:20 ` [PATCH] Introduce git version --list-features " Shawn O. Pearce
2007-05-31 0:25 ` Johannes Schindelin
2007-05-31 6:50 ` Alex Riesen
2007-05-31 13:30 ` Shawn O. Pearce
2007-05-31 23:46 ` Junio C Hamano
2007-06-01 3:09 ` Shawn O. Pearce
2007-06-01 3:57 ` Junio C Hamano
2007-06-01 4:14 ` Shawn O. Pearce
2007-06-01 7:13 ` Johannes Sixt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 4:59 Shawn O. Pearce
2007-06-21 5:47 ` Junio C Hamano
2007-06-21 6:10 ` Shawn O. Pearce
2007-06-21 7:02 ` Junio C Hamano
2007-06-21 11:58 ` 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=465FC735.C78ACD5@eudaptics.com \
--to=j.sixt@eudaptics.com \
--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 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.