blob: 97e77084a2b0dca4cacd2cbb103952bea3f2b82f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
|
change ... closed
=================
With this error message Gerrit rejects to push a commit to a change
that is already closed.
This error occurs if you are trying to push a commit that contains
the Change-Id of a closed change in its commit message. A change can
be closed either because it was already submitted and merged or
because it was deferred or abandoned.
If the change for which you wanted to upload a new patch set was
already submitted and merged you may want to push your commit as a
new change. To do this you have to remove the Change-Id from the
commit message as explained link:error-push-fails-due-to-commit-message.html[here] and ideally generate a new Change-Id
using the link:cmd-hook-commit-msg.html[commit hook] or EGit. Before pushing again it is also
recommendable to do a link:http://www.kernel.org/pub/software/scm/git/docs/git-rebase.html[git rebase] to base your commit on the submitted
change. Pushing again should now create a new change in Gerrit.
If the change for which you wanted to upload a new patch set was
deferred or abandoned and your new changes overcome the reasons for
deferring/abandoning this change you may want to restore the change
in the Gerrit WebUI (browse the deferred/abandoned change in the
Gerrit WebUI and click on the 'Restore Change' button). Afterwards
the push should succeed and a new patch set for this change will be
created.
GERRIT
------
Part of link:error-messages.html[Gerrit Error Messages]
|
