{"thread":{"id":"50742","subject":"Misleading error message with invalid filename on Windows","startedAt":"2019-03-14T22:31:38Z","lastAt":"2019-03-14T22:31:38Z","messageCount":1,"participants":["Josh Mandel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"371549","messageId":"CANSMLKELiaTR81zscG6Or9psL2ZLizAtYEqT72WGHdY92sAFQA@mail.gmail.com","threadId":"50742","inReplyTo":"CANSMLKFUXza=qj14gOd+jzX+R+R_JDO8XqmrjXYukB9s0FDhMQ@mail.gmail.com","subject":"Misleading error message with invalid filename on Windows","fromName":"Josh Mandel","fromEmail":"jmandel@gmail.com","sentAt":"2019-03-14T22:31:19Z","receivedAt":"2019-03-14T22:31:38Z","isPatch":false,"sender":{"key":"jmandel@gmail.com","avatar":null},"body":"Running git 2.21.0 on Windows with certain invalid file names like\n\"c:\\root.txt\" (see https://github.com/jmandel/local-path-test as a\ntest case), I get an expected \"invalid path\" error when I clone the\nrepository.\n\nBut if I actually have a file at this path (i.e., outside of the git\nworking tree, at root of my file system) then I instead receive a\ndifferent error message:\n\n$ touch /c/root.txt\n$ git clone https://github.com/jmandel/local-path-test.git\n\n> error: Untracked working tree file 'c:\\root.txt' would be overwritten by merge.\n\nThis error message is misleading, in that (if I understand correctly)\nthere's actually no danger of my local file (which is *not* in the\nworking tree at all) being overwritten.\n\nBest,\nJosh\n"}]}