61698b14e0
We previous use the section title style like: Section level 1 =============== Section level 2 --------------- Which have a problem in Asciidoctor that the number of "="s or "-"s must match the number of characters in the header exactly, as a result it's easy to make mistakes while changing the titles. Asciidoctor provides a better style like: = Section level 1 == Section level 2 So we switched to this style. Also fixed a bug in replace_macros.py, which will not cause any problem in the old style. Change-Id: I811dd7238735d98f662767c17086152cd69aea02
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
= multiple Change-Id lines in commit message footer
|
|
|
|
With this error message Gerrit rejects to push a commit if the commit
|
|
message footer of the pushed commit contains several Change-Id lines.
|
|
|
|
You can see the commit messages for existing commits in the history
|
|
by doing a link:http://www.kernel.org/pub/software/scm/git/docs/git-log.html[git log].
|
|
|
|
If it was the intention to rework a change and to push a new patch
|
|
set, find the change in the Gerrit WebUI, copy its Change-Id line and
|
|
use the copied Change-Id line instead of the existing Change-Id lines
|
|
in the commit message of the commit for which the push is failing.
|
|
How to do this is explained link:error-push-fails-due-to-commit-message.html#commit_hook[here].
|
|
|
|
If it was the intention to create a new change in Gerrit simply
|
|
remove all Change-Id lines from the commit message of the
|
|
commit for which the push is failing. How to do this is explained
|
|
link: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
|
|
will be automatically generated and inserted.
|
|
|
|
|
|
== SEE ALSO
|
|
|
|
* link:user-changeid.html[Change-Id Lines]
|
|
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:error-messages.html[Gerrit Error Messages]
|
|
|
|
SEARCHBOX
|
|
---------
|