From: Mark Levedahl <mlevedahl@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: paulus@samba.org, git@vger.kernel.org, Eric Blake <ebb9@byu.net>
Subject: Re: [PATCH] gitk - work around stderr redirection on Cygwin
Date: Sun, 13 Jul 2008 17:53:13 -0400 [thread overview]
Message-ID: <487A7949.9050800@gmail.com> (raw)
In-Reply-To: <7vfxqdqxh7.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Mark Levedahl <mlevedahl@gmail.com> writes:
>
>
>> 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).
>>
>
> In the meantime, is it an option to apply this as a port specific patch
> when Cygwin and whichever distribution ship with old Tcl package their
> binary releases?
>
> Just checking how urgent this issue is (8.4.1 was from Oct 2002 if I am
> not mistaken) for maintainers of Cygwin port, and I am suspecting that
> kernel folks are somewhat busy near/around OLS/KS timeframe (but not me).
>
>
(I didn't trim the message as I've copied the Cygwin git maintainer).
I certainly have this patch in my tree so the folks I supply git to who
use Cygwin have this patch. The question of whether to maintain this out
of tree for the official Cygwin release is up to Eric.
Mark
next prev parent reply other threads:[~2008-07-13 21:54 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
2008-07-13 21:35 ` Junio C Hamano
2008-07-13 21:53 ` Mark Levedahl [this message]
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=487A7949.9050800@gmail.com \
--to=mlevedahl@gmail.com \
--cc=ebb9@byu.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).