From: Mark Levedahl <mlevedahl@gmail.com>
To: Eric Blake <ebb9@byu.net>
Cc: Junio C Hamano <gitster@pobox.com>,
paulus@samba.org, git@vger.kernel.org
Subject: Re: [PATCH] gitk - work around stderr redirection on Cygwin
Date: Thu, 17 Jul 2008 22:41:47 -0400 [thread overview]
Message-ID: <488002EB.8080100@gmail.com> (raw)
In-Reply-To: <487EC2BB.5050503@byu.net>
Eric Blake wrote:
> Could you point me to the patch? I need to roll the Cygwin git
> release of
> 1.5.6.3 anyway (in part because cygwin has upgraded from perl 5.8 to
> 5.10). This sounds like something worth me including as a vendor patch,
> if it does not get folded into the main repo.
>
The patch is at the top of this thread:
http://article.gmane.org/gmane.comp.version-control.git/85023/match=gitk+work+around+stderr+redirection
(I'll send you a patch against Junio's tree privately as a backup).
Mark
prev parent reply other threads:[~2008-07-18 2:43 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
2008-07-17 3:55 ` Eric Blake
2008-07-18 2:41 ` Mark Levedahl [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=488002EB.8080100@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 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.