From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Sixt <J.Sixt@eudaptics.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Work around a bad interaction between Tcl and cmd.exe with "^{tree}"
Date: Thu, 12 Jul 2007 02:47:38 -0400 [thread overview]
Message-ID: <20070712064738.GT4436@spearce.org> (raw)
In-Reply-To: <4693AF6C.99DB933@eudaptics.com>
Johannes Sixt <J.Sixt@eudaptics.com> wrote:
> It seems that MSYS's wish does some quoting for Bourne shells, in
> particular, escape the first '{' of the "^{tree}" suffix, but then it uses
> cmd.exe to run "git rev-parse". However, cmd.exe does not remove the
> backslash, so that the resulting rev expression ends up in git's guts
> as unrecognizable garbage: rev-parse fails, and git-gui hickups in a way
> that it must be restarted.
Finally fixed in git-gui 0.7.5, which I just pushed out.
--
Shawn.
next prev parent reply other threads:[~2007-07-12 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 16:10 [PATCH] Work around a bad interaction between Tcl and cmd.exe with "^{tree}" Johannes Sixt
2007-07-11 8:03 ` Shawn O. Pearce
2007-07-12 6:47 ` Shawn O. Pearce [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-10 13:09 Johannes Sixt
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=20070712064738.GT4436@spearce.org \
--to=spearce@spearce.org \
--cc=J.Sixt@eudaptics.com \
--cc=git@vger.kernel.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).