commit 13ec236026ca7434479884eab6a8e4ea7047aaa5
author Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com> Tue Mar 01 13:21:33 2016 -0300
committer Andrew Gerrand <adg@golang.org> Sat May 28 03:12:11 2016 +0000
tree 20791aa4c1eac13dd495412dd127ce67e2984a79
parent b7f20f28bc89a6599ce258f2705ac8e1351ab28d

git-codereview: make change fail with multiple pending changes

When using 'git change' to amend the current change, it will fail
if there are multiple pending changes. The previous behavior (amending
the latest) wasn't always what the user intended.

    $ git change
    git-codereview: cannot amend change: multiple changes pending:
    	fc60fd5 test: dummy change
    	6440cdc git-codereview: make change fail with multiple pending changes
    $

Unlike mail and submit, change doesn't support explicitly telling
which commit to work on. Either 'git commit --amend' (for updating
the topmost change) or a combination of 'git commit' and 'git rebase'
must be used.

Fixes golang/go#10443.

Change-Id: I2f6ea1b0e302b66b627761d72d031a3b6aa0fba2
Reviewed-on: https://go-review.googlesource.com/20049
Reviewed-by: Andrew Gerrand <adg@golang.org>
Run-TryBot: Andrew Gerrand <adg@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>