Skip to content

BreakingChanges: say that git diff X..Y syntax will be removed in 3.0 #1989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Open
martinvonz wants to merge 1 commit into
base: master
Choose a base branch
from
Open

BreakingChanges: say that git diff X..Y syntax will be removed in 3.0 #1989

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
BreakingChanges: say that git diff X..Y syntax will be removed in 3.0 
The `git diff X..Y` syntax is quite misleading because it looks like
it shows the diff of the commits in the X..Y range but it actually
shows the diff from X to Y. IMO, if that syntax is supported, it
should show a diff from the merge base of X and Y to Y. I hope Git 3.0
is a good time to remove support for the current syntax and
semantics. Then we can perhaps add the syntax back later with less
surprising semantics.

Signed-off-by: Martin von Zweigbergk <[email protected]>
  • Loading branch information
@martinvonz
martinvonz committed Oct 15, 2025
commit daedd978b1aec06ab090ba119334f584d6d7e579
4 changes: 4 additions & 0 deletions Documentation/BreakingChanges.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,10 @@ applications and forges.
+
There is no plan to deprecate the "sha1" object format at this point in time.
+
Support for "git diff X..Y" syntax will be removed. Use "git diff X Y" instead.
This will open up the syntax for a more consistent interpretation of
"git diff $(git merge-base X Y) Y".
+
Cf. <[email protected]>,
<[email protected]>,
<CA+EOSBncr=4a4d8n9xS4FNehyebpmX8JiUwCsXD47EQDE+DiUQ@mail.gmail.com>.
Expand Down
Loading