blob: f19ebddd453a1158396fae8ca1436126f3777b54 [file] [log] [blame]
Marian Harbachebeb1542019-12-13 10:42:46 +01001:linkattrs:
Han-Wen Nienhuysb8424a02018-08-27 20:04:08 +02002= commit xxxxxxx: multiple Change-Id lines in message footer
Edwin Kempin947d6662010-12-27 13:33:09 +01003
4With this error message Gerrit rejects to push a commit if the commit
David Pursehousea68769e2012-11-07 12:36:17 +09005message footer of the pushed commit contains several Change-Id lines.
Edwin Kempin947d6662010-12-27 13:33:09 +01006
7You can see the commit messages for existing commits in the history
Marian Harbach34253372019-12-10 18:01:31 +01008by doing a link:http://www.kernel.org/pub/software/scm/git/docs/git-log.html[git log,role=external,window=_blank].
Edwin Kempin947d6662010-12-27 13:33:09 +01009
10If it was the intention to rework a change and to push a new patch
David Pursehousea1d633b2014-05-02 17:21:02 +090011set, find the change in the Gerrit Web UI, copy its Change-Id line and
Edwin Kempin947d6662010-12-27 13:33:09 +010012use the copied Change-Id line instead of the existing Change-Id lines
13in the commit message of the commit for which the push is failing.
14How to do this is explained link:error-push-fails-due-to-commit-message.html#commit_hook[here].
15
16If it was the intention to create a new change in Gerrit simply
17remove all Change-Id lines from the commit message of the
18commit for which the push is failing. How to do this is explained
19link:error-push-fails-due-to-commit-message.html#commit_hook[here]. In case you have configured the link:cmd-hook-commit-msg.html[commit hook] a new Change-Id
20will be automatically generated and inserted.
21
22
Yuxuan 'fishy' Wang61698b12013-12-20 12:55:51 -080023== SEE ALSO
Edwin Kempin947d6662010-12-27 13:33:09 +010024
25* link:user-changeid.html[Change-Id Lines]
26
27
28GERRIT
29------
30Part of link:error-messages.html[Gerrit Error Messages]
Yuxuan 'fishy' Wang99cb68d2013-10-31 17:26:00 -070031
32SEARCHBOX
33---------