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 commits that are not cherry-picked between branch $1 and $2. Example 1, show commits for 2.8, not existing in 2.7; practical for collecting of the changelog: cherry2 calligra/2.7 calligra/2.8 Example 2, show commits in master, not existing in 2.8, useful to see what's going on post-2.8.x: cherry2 calligra/2.8 master I am grepping output of these commands for 'kexi' in the paths, etc. -- regards / pozdrawiam, Jaroslaw Staniek Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org Qt for Tizen | http://qt-project.org/wiki/Tizen Qt Certified Specialist | http://www.linkedin.com/in/jstaniek _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
