From: Andreas Schrell <as@schrell.de>
Date: Mon, 28 Nov 2022 13:10:41 GMT
Subject: Program path added to sparse file specification if leading slash is used
Message-ID: <db69818f32a2723cb7ef9ddf79d3ae39@schrell.de>

Hi,

What did you do before the bug happened? (Steps to reproduce your issue)

$ git sparse-checkout set /Workspace/Build/Pipeline $ git 
sparse-checkout list C:/Program Files/Git/Workspace/Build/Pipeline

$ git sparse-checkout set Workspace/Build/Pipeline $ git sparse-checkout 
list Workspace/Build/Pipeline

What did you expect to happen? (Expected behavior) The program path 
should not be included in the file spec, if I set the leading slash

What happened instead? (Actual behavior) The git program path was added 
in the sparce file spec.

What's different between what you expected and what actually happened?

Wrong path

Anything else you want to add:

Please review the rest of the bug report below.

You can delete any lines you don't wish to share.

[System Info]

git version:

git version 2.38.1.windows.1

cpu: x86_64

built from commit: b85c8f604d375d4d773a36842964e8a7ec056aae

sizeof-long: 4

sizeof-size_t: 8

shell-path: /bin/sh

feature: fsmonitor--daemon

uname: Windows 10.0 19045

compiler info: gnuc: 12.2

libc info: no libc information available $SHELL (typically, interactive 
shell): C:\Program Files\Git\usr\bin\bash.exe

[Enabled Hooks]

Mit freundlichen Grüßen

Andreas Schrell

Software Engineer