Remove --force-message option from the review command

Since 8c850ec the review message is always added even if labels
could not be applied, making the `--force-message` option redundant.

Remove the option from the command and the documentation.

Change-Id: Id10f8f4dc77988670584dea622e6708942320780
This commit is contained in:
David Pursehouse 2013-05-01 11:05:51 +09:00
parent 9240c299f0
commit c271318577
2 changed files with 0 additions and 21 deletions

View File

@ -11,7 +11,6 @@ SYNOPSIS
'ssh' -p <port> <host> 'gerrit review'
[--project <PROJECT> | -p <PROJECT>]
[--message <MESSAGE> | -m <MESSAGE>]
[--force-message]
[--submit | -s]
[--abandon | --restore]
[--publish]
@ -51,22 +50,6 @@ OPTIONS
Optional cover letter to include as part of the message
sent to reviewers when the approval states are updated.
--force-message::
Option which allows Gerrit to publish the --message, even
when the labels could not be applied due to the change being
closed.
+
Used by some scripts/CI-systems, where the results (or links
to the result) are posted as a message after completion of a
build (often together with a label-change, indicating the success
of the build).
+
If the message is posted successfully, the command will return
successfully, even if the label could not be changed.
+
This option will not force the message to be posted if the command
fails because the user is not permitted to change the label.
--help::
-h::
Display site-specific usage information, including the

View File

@ -105,10 +105,6 @@ public class ReviewCommand extends SshCommand {
@Option(name = "--submit", aliases = "-s", usage = "submit the specified patch set(s)")
private boolean submitChange;
@Option(name = "--force-message", usage = "publish the message, "
+ "even if the label score cannot be applied due to the change being closed")
private boolean forceMessage = false;
@Option(name = "--publish", usage = "publish the specified draft patch set(s)")
private boolean publishPatchSet;