On Thu, Oct 10, 2013 at 7:57 PM, Johannes Sixt <j...@kdbg.org> wrote:

>> test-path-utils I get this on Windows Server 2008 R2 64-bit:
>> $ test-path-utils mingw_path /a/b/
>> a:/b/
>> But if I install [1] on my local Windows 8 64-bit I get:
>> $ test-path-utils mingw_path /a/b/
>> C:/msysgit/msysGit/a/b/
> Interesting. I guess that you get consistent behavior when the first
> path component is not merely a single letter, e.g., /foo/bar.

You're right! With /foo/bar on W2k8r2 I get

$ test-path-utils mingw_path /foo/bar/

> Do you have a drive a: configured somewhere in your MSYS environment on
> the 2k8r2 machine? See /etc/fstab. Do you have a floppy drive in that
> machine?

Again you're correct. The W2k8r2 machine actually is a VM, providing a
floppy drive "A:". So the obvious thing would be to replace /a/b/ with
/foo/bar/ in the tests, but that just masks the problem, or?

PS: I'm also quite unhappy about naming the function "mingw_path". The
path mangling comes from MSYS, not MinGW, so if at all it should be
named msys_path. But as the code for the "mingw_path" function does
nothing either MSYS or MinGW related but just prints argv[2] as it was
passed to main() it should probably simply called "print_path".

Sebastian Schuberth
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to