We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$ git --version --build-options git version 2.36.0.windows.1 cpu: x86_64 built from commit: ea1e13f73339d57cbe81a0bae6fba669aaccf656 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon
$ cmd.exe /c ver Microsoft Windows [Version 10.0.22000.739]
> type "C:\Program Files\Git\etc\install-options.txt" Editor Option: Notepad Custom Editor Path: Default Branch Option: Path Option: Cmd SSH Option: ExternalOpenSSH Tortoise Option: false CURL Option: WinSSL CRLF Option: CRLFCommitAsIs Bash Terminal Option: MinTTY Git Pull Behavior Option: FFOnly Use Credential Manager: Enabled Performance Tweaks FSCache: Enabled Enable Symlinks: Enabled Enable Pseudo Console Support: Disabled Enable FSMonitor: Disabled
Not that I can think of.
PowerShell Core 7.2.4
mkdir foo pushd foo git init echo a > a.txt git add a.txt git commit -m a echo b > b.txt git add b.txt git commit -m b echo aa > a.txt echo bb > b.txt git add a.txt b.txt git commit -m ab gitk Find commit touching paths: a.txt
Only commits a and ab are highlighted.
a
ab
Commits b and ab are highlighted.
b
The text was updated successfully, but these errors were encountered:
This regression in git diff-tree --stdin has been fixed in Git 2.36.1.
git diff-tree --stdin
Duplicate of #3815
Sorry, something went wrong.
No branches or pull requests
Setup
defaults?
to the issue you're seeing?
Not that I can think of.
Details
PowerShell Core 7.2.4
Minimal, Complete, and Verifiable example
this will help us understand the issue.
Only commits
a
andab
are highlighted.Commits
b
andab
are highlighted.The text was updated successfully, but these errors were encountered: