From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: git and absolute Windows-style paths
Date: Tue, 19 Apr 2016 22:28:00 -0000 [thread overview]
Message-ID: <5716A9FA.6020407@cornell.edu> (raw)
In-Reply-To: <892b8f62-266a-da20-c8f4-4b2b82a66c39@gmail.com>
On 4/19/2016 5:31 PM, Marco Atzeri wrote:
> On 19/04/2016 22:34, silverwind wrote:
>> Hey,
>>
>> I noticed that Cygwin's git does not seem to correctly process
>> Windows-style paths in at least v2.7.4 and v2.8.1. It may have worked
>> before, but I'm not totally certain.
>
> don't assume cygwin programs are able to process windows path.
> Most don't. Use Posix paths
But I think the OP is correct in pointing out that git should have given
an error, as it does when a Posix path points to a non-existent file:
$ git add foo
fatal: pathspec 'foo' did not match any files
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-04-19 21:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 21:00 silverwind
2016-04-19 21:58 ` Marco Atzeri
2016-04-19 22:28 ` Ken Brown [this message]
2016-04-20 10:28 ` Adam Dinwoodie
2016-04-20 0:49 ` Bill Smith
2016-04-20 15:52 ` silverwind
2016-04-20 16:06 ` Eliot Moss
2016-04-20 16:15 ` Brian Clifton
2016-04-20 18:18 ` Ernie Rael
2016-04-20 20:39 ` Eliot Moss
2016-04-20 21:17 ` Adam Dinwoodie
2016-04-21 19:50 ` Andrey Repin
2016-04-20 23:40 ` Ernie Rael
2016-04-21 0:14 ` Eliot Moss
2016-04-21 15:19 ` Ray Donnelly
2016-04-21 16:01 ` Ray Donnelly
2016-04-20 16:46 ` silverwind
2016-04-20 16:56 ` Adam Dinwoodie
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=5716A9FA.6020407@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).