On Sat, Mar 24, 2012 at 9:21 PM, Marcin Cieslak saper@saper.info wrote:
When playing with moving (cherry picking) commits from master to one of the release branches (REL1_19) I noticed that "git cherry-pick" and "git merge" do not invoke "commit-msg" hook and therefore don't add Change-Id to the commits.
This is normally not a problem for people who are allowed changes without "Change-Id" to the repository (i.e. trunk gatekeepers), but this may add some problems for committers at large.
This is an issue that has been known to us for some time, but I guess it was never documented properly. Running git commit --amend after a merge or cherry-pick has always added a Change-Id for me.
Roan