From: Pat Thoyts <patthoyts@googlemail.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org,
msysGit Mailinglist <msysgit@googlegroups.com>
Subject: Re: [msysGit] [GIT GUI PATCH] git-gui: fix open explorer window on Windows 7
Date: Wed, 24 Feb 2010 12:15:03 +0000 [thread overview]
Message-ID: <a5b261831002240415l5447ac94wd80c162fc9492fd5@mail.gmail.com> (raw)
In-Reply-To: <20100223225243.GC11271@book.hvoigt.net>
On 23 February 2010 22:52, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> It seems that Windows 7's explorer is not capable to cope with paths
> that contain forward slashes as path seperator. We thus substitute slash
> with the platforms native backslash.
>
What bug are you actually addressing here? How can I reproduce it? My
experience on Windows 7 is that there is no problem but I assume I'm
doing a different operation. If I use the git-gui "Explore working
copy" it opens the Windows explorer for me just fine.
next prev parent reply other threads:[~2010-02-24 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:52 [GIT GUI PATCH] git-gui: fix open explorer window on Windows 7 Heiko Voigt
2010-02-24 0:14 ` Markus Heidelberg
2010-02-24 6:22 ` Giuseppe Bilotta
2010-02-24 12:12 ` [msysGit] " Pat Thoyts
2010-02-25 0:14 ` [PATCH] git-gui: fix "Explore Working Copy" for Windows again Markus Heidelberg
2010-02-25 20:44 ` Heiko Voigt
2010-02-25 23:00 ` Pat Thoyts
2010-02-26 0:46 ` Johannes Schindelin
2010-02-27 21:14 ` Heiko Voigt
2010-02-24 12:15 ` Pat Thoyts [this message]
2010-02-25 20:30 ` Re: [GIT GUI PATCH] git-gui: fix open explorer window on Windows 7 Heiko Voigt
2010-02-25 22:23 ` [msysGit] " Markus Heidelberg
2010-02-25 22:49 ` Pat Thoyts
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=a5b261831002240415l5447ac94wd80c162fc9492fd5@mail.gmail.com \
--to=patthoyts@googlemail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=msysgit@googlegroups.com \
--cc=spearce@spearce.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).