| Issue 1522: | Pushing an open change properly closes it but replies otherwise | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.4.2 What steps will reproduce the problem? 1. publish a change 2. push that same change $ git push origin HEAD:refs/for/master Counting objects: 5, done. Delta compression using up to 2 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 299 bytes, done. Total 3 (delta 1), reused 0 (delta 0) remote: Resolving deltas: 100% (1/1) remote: Processing changes: new: 1, done remote: remote: New Changes: remote: http://git/r/18047 remote: To ssh://git/internal/test * [new branch] HEAD -> refs/for/master $ git push origin master Total 0 (delta 0), reused 0 (delta 0) remote: Processing changes: closed: 1, refs: 2, done To ssh://git/internal/test ! [remote rejected] master -> master (change 18047 closed) error: failed to push some refs to 'ssh://git/internal/test' Yet the change is properly closed and immediately doing a "git fetch" shows that master has been properly updated. Please provide any additional information below. I just upgraded from 2.3 to 2.4.2, otherwise no changes have been made. I never saw this issue with 2.3. I'm using H2. The client is git 1.7.11.3.
Aug 10, 2012
Project Member
#1
jaysoff...@gmail.com
Aug 10, 2012
(No comment was entered for this change.)
Status:
Duplicate
Mergedinto: 1493 |
|
| ► Sign in to add a comment |