From: Mark Levedahl <mlevedahl@gmail.com>
To: Mark Levedahl <mlevedahl@gmail.com>,
paulus@samba.org, Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk - work around stderr redirection on Cygwin
Date: Sun, 13 Jul 2008 16:37:20 -0400 [thread overview]
Message-ID: <487A6780.7030500@gmail.com> (raw)
In-Reply-To: <1213462668-424-1-git-send-email-mlevedahl@gmail.com>
Mark Levedahl wrote:
> Cygwin is *still* shipping with antiquated Tcl 8.4.1, and will continue
> to do so for the indefinite future. This version does not understand
> the "2>@1" redirection syntax, so such redirection of stderr must be
> done using sh.
>
Ping. This bug is in 1.5.6.x, and thus also in the current Cygwin git
release: as a result, several gitk context menu items cause errors. (Let
me know if I should resend the patch).
Mark
next prev parent reply other threads:[~2008-07-13 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 16:57 [PATCH] gitk - work around stderr redirection on Cygwin Mark Levedahl
2008-07-13 20:37 ` Mark Levedahl [this message]
2008-07-13 21:35 ` Junio C Hamano
2008-07-13 21:53 ` Mark Levedahl
2008-07-17 3:55 ` Eric Blake
2008-07-18 2:41 ` Mark Levedahl
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=487A6780.7030500@gmail.com \
--to=mlevedahl@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=paulus@samba.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).