Hi, Jaroslaw!
I usually use the git cherry command to find out what commits are not yet
ported. It uses some nice commit-diff algorithm so unless the commit was
modified while cherry-picking it'll be reported correctly.
git cherry -v HEAD origin/master
I usually combine it with emacs and it's 'h
And the script...
cherry2
Description: Binary data
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hello,
Usual "git log X..Y -- {path}" shows commits for {path} between tags X and Y.
What if we have no tags or commit hashes or (better) we're cherry-picking?
The latter results in duplicated hashes.
If this is not just my git-ignorance, I have coined a simple script
cherry2 (attached).
It shows
