From a0195d8d4167a6430c2f4089d9aea3d1b51bb48f Mon Sep 17 00:00:00 2001
From: Alex Dadgar <alex.dadgar@gmail.com>
Date: Thu, 22 Mar 2018 14:49:08 -0700
Subject: [PATCH] remove comment

---
 command/operator_autopilot.go | 29 -----------------------------
 1 file changed, 29 deletions(-)

diff --git a/command/operator_autopilot.go b/command/operator_autopilot.go
index 49fef0bc4..64e076319 100644
--- a/command/operator_autopilot.go
+++ b/command/operator_autopilot.go
@@ -38,33 +38,4 @@ Usage: nomad operator autopilot <subcommand> [options]
   Please see the individual subcommand help for detailed usage information.
   `
 	return strings.TrimSpace(helpText)
-	/*
-			helpText := `
-		Usage: nomad deployment <subcommand> [options] [args]
-
-		  This command groups subcommands for interacting with deployments. Deployments
-		  are used to manage a transistion between two versions of a Nomad job. Users
-		  can inspect an ongoing deployment, promote canary allocations, force fail
-		  deployments, and more.
-
-		  Examine a deployments status:
-
-		      $ nomad deployment status <deployment-id>
-
-		  Promote the canaries to allow the remaining allocations to be updated in a
-		  rolling deployment fashion:
-
-		      $ nomad deployment promote <depoloyment-id>
-
-		  Mark a deployment as failed. This will stop new allocations from being placed
-		  and if the job's upgrade stanza specifies auto_revert, causes the job to
-		  revert back to the last stable version of the job:
-
-		      $ nomad deployment fail <depoloyment-id>
-
-		  Please see the individual subcommand help for detailed usage information.
-		`
-
-			return strings.TrimSpace(helpText)
-	*/
 }