Issue 1691: Gerrit creates empty patchsets after rebase and pushing a new commit.
Status:  New
Owner: ----
Reported by siemens1993@gmail.com, Nov 29, 2012
Affected Version: 2.4.2

What steps will reproduce the problem?
1. Submit a commit for code review.
2. Do some changes to the commit using `git rebase -i` and the `edit` option.
3. Push the changed commit (1) to gerrit.
4. Now push a more recent commit (2) to gerrit for code review.

What is the expected output? What do you see instead?
Expected: Only commit (2) is affected by step 5.
Instead: All commits commited for code review between (1) and (2) are getting new, empty patch sets.

Please provide any additional information below.
Used workflow for pushing a commit to gerrit:

git fetch
git rebase origin/develop
git push origin <sha>:refs/for/develop

Any pointers, on how to solve this problem are welcome.
Thanks,
Markus
May 28, 2014
#1 Ian.Kuml...@gmail.com
We have seen this on people rebasing after a commit was actually merged.

If the rebase is empty, it shouldn't be posted