From: Eris Belew <erisrenee@gmail.com>
To: git@vger.kernel.org
Subject: Bug: Pathspec parsing on Windows fails when branch specified
Date: Wed, 20 Nov 2013 13:09:26 -0800 [thread overview]
Message-ID: <CAM8h_A_zfX4U8hGxiw3_79zMZXmcTN3CPRUcrtsQTQdD4RaMhQ@mail.gmail.com> (raw)
System: Windows Server 2008 R2
Git: git version 1.8.4.msysgit.0
Shell: Powershell V3 (No third-party modules loaded)
Summary:
When specifying a pathspec including a branch/commit, path separator
characters are not translated. Since tab-completion in windows shells (ex:
CMD, PowerShell, not unix-style shells running on windows) uses the windows
path separator, and other git commands work fine with the windows path
separator, the expected behavior would be to translate for me.
Reproduction:
git diff BRANCH:path\to\file path\to\file
Result:
fatal: Path 'path\to\file' does not exist in 'BRANCH'
Expected:
Normal diff operation
Workaround:
Manually convert pathspec. Examples of working command:
git diff BRANCH:path/to/file path\to\otherfile
git diff BRANCH:path/to/file path/to/otherfile
Thanks,
Eris
next reply other threads:[~2013-11-20 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 21:09 Eris Belew [this message]
2013-11-20 22:12 ` Bug: Pathspec parsing on Windows fails when branch specified 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=CAM8h_A_zfX4U8hGxiw3_79zMZXmcTN3CPRUcrtsQTQdD4RaMhQ@mail.gmail.com \
--to=erisrenee@gmail.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).