From: Andreas Schrell <as@schrell.de>
To: git@vger.kernel.org
Subject: Program path added to sparse file specification if leading slash is used
Date: Mon, 28 Nov 2022 14:10:41 +0100 [thread overview]
Message-ID: <db69818f32a2723cb7ef9ddf79d3ae39@schrell.de> (raw)
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
next reply other threads:[~2022-11-28 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:10 Andreas Schrell [this message]
2022-12-09 7:57 ` Program path added to sparse file specification if leading slash is used Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db69818f32a2723cb7ef9ddf79d3ae39@schrell.de \
--to=as@schrell.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).