29 Feb
2012
29 Feb
'12
8:23 p.m.
On Wednesday 29 February 2012, Iñaki Baz Castillo wrote:
I expected that the commit to 3.2 branch would refer
the original
master commit "2e96a72c3b16ccf7a1854eb83be3c779474bee3b" in some way,
but it has become a new commit
"7f2e9173caf0da18bbd2fbad76f855c6bf5703bf".
Hi Iñaki,
normally it should be visible in the commit log, the cherry-pick cmd should
inserts the old log msg + a reference to the original commit id. That the
cherry-picked commit in the stable branch gets a new commit id is the normal
behaviour of git.
Viele Grüße/ best regards,
Henning Westerholt