The documentation says: "Since git -cherry compares the change set rather than the commit identifier (sha1), you can use git -cherry to find out if a local action has been applied associated with another commit identifier."
We will see:
$ git cherry master release-1.1.0 | head -1 - 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 $ git show 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 ... (cherry picked from commit 409c61b3304373a73c787fdf9c08cc338934b74d) ...
git shows the same set of changes for 409c .. and 533e
$ git br --contains 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 release-1.1.0 $ git br --contains 409c61b3304373a73c787fdf9c08cc338934b74d master release-1.0.4
This means that the change set is in both master and release-1.1.0. So why does git cherry show 533e ..?
: " , git -patch-id". , , ?
, git -patch-id , , .
:
git show 533e2559342910fbffa2be5b38fdd7f2ddb2ed53 | git-patch-id git show 409c61b3304373a73c787fdf9c08cc338934b74d | git-patch-id
sha1, git -patch-id, , , .
Caveat lector - , , man-.