On 4/20/16 10:59 PM, Adam Dinwoodie wrote:
native Windows and Cygwin. It's been a while since I tried it, but I
_think_ you can generally use Cygwin Git and Windows Git on the same
working copy without any difficulties, at least if you avoid the common
pain points like line ending rewriting and
I think the "correct" fix would be to get npm (or possibly the
JavaScript engine itself?) to stop acting as if it's in a Windows
environment
You're on the right track. The root issue is that Node.js (on which npm
runs) is a native Windows binary in pretty much all cases, as it's not
possible to
Hey,
I think that tackling this with a script/function is a better approach ...
That's seems like a bandaid solution from which the general user base
would not be able to profit. I think a floating patch to Cygwin's git
package would be more appropriate, unless it can be addressed in
Cygwin
Hey,
Does it work if you do:
git add c:/test/file
Nope, won't work either. No file is added, exit code 0 is given.
> I can't immediately see what's going wrong, so I'm going to report
this upstream.
Thanks. I came upon this issue through npm which is using these Windows
paths for certain
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.
Interestingly, a command like "git add" still sets an 0 exit code
despite the apparent failure. Could it be that some
5 matches
Mail list logo
