{"thread":{"id":"58864","subject":"Program path added to sparse file specification if leading slash is used","startedAt":"2022-11-28T13:19:08Z","lastAt":"2022-12-09T07:57:32Z","messageCount":2,"participants":["Andreas Schrell","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"468089","messageId":"db69818f32a2723cb7ef9ddf79d3ae39@schrell.de","threadId":"58864","inReplyTo":null,"subject":"Program path added to sparse file specification if leading slash is used","fromName":"Andreas Schrell","fromEmail":"as@schrell.de","sentAt":"2022-11-28T13:10:41Z","receivedAt":"2022-11-28T13:19:08Z","isPatch":false,"sender":{"key":"as@schrell.de","avatar":null},"body":"Hi,\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n\n$ git sparse-checkout set /Workspace/Build/Pipeline $ git \nsparse-checkout list C:/Program Files/Git/Workspace/Build/Pipeline\n\n$ git sparse-checkout set Workspace/Build/Pipeline $ git sparse-checkout \nlist Workspace/Build/Pipeline\n\nWhat did you expect to happen? (Expected behavior) The program path \nshould not be included in the file spec, if I set the leading slash\n\nWhat happened instead? (Actual behavior) The git program path was added \nin the sparce file spec.\n\nWhat's different between what you expected and what actually happened?\n\nWrong path\n\nAnything else you want to add:\n\nPlease review the rest of the bug report below.\n\nYou can delete any lines you don't wish to share.\n\n[System Info]\n\ngit version:\n\ngit version 2.38.1.windows.1\n\ncpu: x86_64\n\nbuilt from commit: b85c8f604d375d4d773a36842964e8a7ec056aae\n\nsizeof-long: 4\n\nsizeof-size_t: 8\n\nshell-path: /bin/sh\n\nfeature: fsmonitor--daemon\n\nuname: Windows 10.0 19045\n\ncompiler info: gnuc: 12.2\n\nlibc info: no libc information available $SHELL (typically, interactive \nshell): C:\\Program Files\\Git\\usr\\bin\\bash.exe\n\n[Enabled Hooks]\n\nMit freundlichen Grüßen\n\nAndreas Schrell\n\nSoftware Engineer\n"},{"id":"468822","messageId":"s53q2s3o-8nsr-0766-rr8p-6n7ro0o07p69@tzk.qr","threadId":"58864","inReplyTo":"db69818f32a2723cb7ef9ddf79d3ae39@schrell.de","subject":"Re: Program path added to sparse file specification if leading slash is used","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-12-09T07:57:20Z","receivedAt":"2022-12-09T07:57:32Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Andreas,\n\nOn Mon, 28 Nov 2022, Andreas Schrell wrote:\n\n> What did you do before the bug happened? (Steps to reproduce your issue)\n>\n> $ git sparse-checkout set /Workspace/Build/Pipeline\n> $ git sparse-checkout list C:/Program Files/Git/Workspace/Build/Pipeline\n\nFrom Git for Windows' release notes, in the \"Known Issues\" section,\nhttps://github.com/git-for-windows/build-extra/blob/main/ReleaseNotes.md#known-issues:\n\n\n\tIf you specify command-line options starting with a slash,\n\tPOSIX-to-Windows path conversion will kick in converting e.g.\n\t\"/usr/bin/bash.exe\" to \"C:\\Program Files\\Git\\usr\\bin\\bash.exe\". When that\n\tis not desired -- e.g. \"--upload-pack=/opt/git/bin/git-upload-pack\" or\n\t\"-L/regex/\" -- you need to set the environment variable MSYS_NO_PATHCONV\n\ttemporarily, like so:\n\n\t    MSYS_NO_PATHCONV=1 git blame -L/pathconv/ msys2_path_conv.cc\n\n\t    Alternatively, you can double the first slash to avoid\n\t    POSIX-to-Windows path conversion, e.g. \"//usr/bin/bash.exe\".\n\nCiao,\nJohannes\n"}]}