From 967e2c37267dbad4c45108db902e62defc2377aa Mon Sep 17 00:00:00 2001 From: Edwin Kempin Date: Mon, 10 Jan 2011 13:30:10 +0100 Subject: [PATCH] Extended "no new changes" error description If this error occurs the documentation recommends to use the commit ID to search in the Gerrit WebUI for the change that contains this commit. Unfortunately if the commit was pushed directly to a branch (without going through code review) there is no change that contains this commit. To avoid confusion this case is now explicitly mentioned in the documentation. Signed-off-by: Edwin Kempin Change-Id: I44d21f5b08d942964f54479b64b2dc5a52d9515e --- Documentation/error-no-new-changes.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/error-no-new-changes.txt b/Documentation/error-no-new-changes.txt index fa5226dab0..4000f7235f 100644 --- a/Documentation/error-no-new-changes.txt +++ b/Documentation/error-no-new-changes.txt @@ -30,6 +30,10 @@ means: commit for this change again 3. if a commit was pushed to one branch you cannot push this commit to another branch +4. if a commit was pushed directly to a branch (without going through + code review) you cannot push this commit once again for code + review (please note that in this case searching by the commit ID + in the Gerrit WebUI will not find any change) If you need to re-push a commit you may rewrite this commit by link:http://www.kernel.org/pub/software/scm/git/docs/git-commit.html[amending] it or doing an interactive link:http://www.kernel.org/pub/software/scm/git/docs/git-rebase.html[git rebase]. By rewriting the