* Program path added to sparse file specification if leading slash is used
@ 2022-11-28 13:10 Andreas Schrell
2022-12-09 7:57 ` Johannes Schindelin
0 siblings, 1 reply; 2+ messages in thread
From: Andreas Schrell @ 2022-11-28 13:10 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Program path added to sparse file specification if leading slash is used
2022-11-28 13:10 Program path added to sparse file specification if leading slash is used Andreas Schrell
@ 2022-12-09 7:57 ` Johannes Schindelin
0 siblings, 0 replies; 2+ messages in thread
From: Johannes Schindelin @ 2022-12-09 7:57 UTC (permalink / raw)
To: Andreas Schrell; +Cc: git
Hi Andreas,
On Mon, 28 Nov 2022, Andreas Schrell wrote:
> 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
From Git for Windows' release notes, in the "Known Issues" section,
https://github.com/git-for-windows/build-extra/blob/main/ReleaseNotes.md#known-issues:
If you specify command-line options starting with a slash,
POSIX-to-Windows path conversion will kick in converting e.g.
"/usr/bin/bash.exe" to "C:\Program Files\Git\usr\bin\bash.exe". When that
is not desired -- e.g. "--upload-pack=/opt/git/bin/git-upload-pack" or
"-L/regex/" -- you need to set the environment variable MSYS_NO_PATHCONV
temporarily, like so:
MSYS_NO_PATHCONV=1 git blame -L/pathconv/ msys2_path_conv.cc
Alternatively, you can double the first slash to avoid
POSIX-to-Windows path conversion, e.g. "//usr/bin/bash.exe".
Ciao,
Johannes
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-12-09 7:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-28 13:10 Program path added to sparse file specification if leading slash is used Andreas Schrell
2022-12-09 7:57 ` Johannes Schindelin
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).