Closed greyHairChooseLife closed 1 year ago
It's not a typo. Two-dot and three-dot rev ranges do not describe the same set of commits.
man git-rev-parse
Take for instance this example commit graph:
Here we have two branches, main
and feature
, that have diverged. If we perform a symdiff on these two branches we get this set of commits:
Using --cherry-pick
options we can specify which side of the symdiff we care about:
oh, I see.
As a beginner, I used to git diff
for staged or unstaged files. Or to compare two of whole branches before I merge just-fetched upstream/*.
Yet no experienced the conflict between two branches but only between some commits when I rebase my own code.
But now your answer made sense to me very well. Thank you for your kindness, despite my dumb issue.
Here is link for the USAGE page.
There you can see right away like below. It has triple dots between git-revs.
:DiffviewFileHistory --range=origin/main...HEAD --right-only --no-merges
I cared nothing but only
--range
. So I set my default like:DiffviewFileHistory --range=origin/main...HEAD
. And it returns me like...from : arbitrary commit (but fixed at least) to : HEAD
And then I found there are only 2 dots for the option
--range
in README and :help page. That made me happy finally.Since I couldn't find anywhere about triple dots for the option, I leave here issue for a typing error.
Thanks for the lovely plugin. God bless you.