| Issue 2008: | Gerrit rejects patches with committer date change and no other change | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.6.1 What steps will reproduce the problem? 1. Commit a set of changes to a local repo. 2. Push them to refs/for/trunk 3. Change one of the commits in the middle of the set of changes using "git rebase --interactive --force" 4. Push to refs/for/trunk What is the expected output? What do you see instead? I expect the success message : * [new branch] HEAD -> refs/for/trunk but actually it fails with a message similar to: ! [remote rejected] HEAD -> refs/for/trunk (no changes made) error: failed to push some refs to 'ssh://user@server:port/repo.name' This appears to be because the committer date has changed for all commits, thereby changing the SHA. Gerrit then seems to fail because the files and commit message have not changed in the first patch. The issue can be worked around by changing the commit message in the first object in the set. The issue could also be worked around by not using --force ... but this is not possible, as I'm actually using TortoiseGit, which currently requires use of --force. Gerrit should be able to cope with a patch that has a different committer date but no other changes.
Jul 17, 2013
Project Member
#1
david.pu...@sonymobile.com
Status:
ChangeUnderReview
Jul 31, 2013
(No comment was entered for this change.)
Status:
New
Sep 18, 2013
(No comment was entered for this change.)
Status:
Duplicate
Mergedinto: 1867 |
|
| ► Sign in to add a comment |