... I would guess this is the same as the rest of the issues that are because the ImDisk driver doesn't look enough like a physical [disk] device, but just in case someone has something else to say, I wanted to mention it. ;)
Needless to say, I am using the ImDisk Toolkit's excellent support for mounting "/tmp" as a RAMdrive on my Windows 10 Pro 64-bit system. :)
Note that this is issued by the "BASH Shell" that is part of the "Git for Windows" project, which states that what they provide is actually a "BASH emulation"... this might mean that I could track down exactly how they are coming up with whatever leads them to issue the above error message, but of course there isn't anything easy like a "bash.c" in their source tree.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Amazingly, I just installed the latest version of "Git for Windows" (2.13.3) and this has been fixed - presumably by the "bash" included there not being quite as picky about what it considers a valid folder. ;)
So, cool, nothing to see here [any longer], move along...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
... I would guess this is the same as the rest of the issues that are because the ImDisk driver doesn't look enough like a physical [disk] device, but just in case someone has something else to say, I wanted to mention it. ;)
Needless to say, I am using the ImDisk Toolkit's excellent support for mounting "/tmp" as a RAMdrive on my Windows 10 Pro 64-bit system. :)
Note that this is issued by the "BASH Shell" that is part of the "Git for Windows" project, which states that what they provide is actually a "BASH emulation"... this might mean that I could track down exactly how they are coming up with whatever leads them to issue the above error message, but of course there isn't anything easy like a "bash.c" in their source tree.
Amazingly, I just installed the latest version of "Git for Windows" (2.13.3) and this has been fixed - presumably by the "bash" included there not being quite as picky about what it considers a valid folder. ;)
So, cool, nothing to see here [any longer], move along...