I am not sure whether this has been reported before. I follow this mailing list, but I don't read all emails in detail, so I could have missed a bug report or a fix for the problem. Anyway, what seems to happen is that some protocol error happens when an automatic GC is triggered during a push. The push succeeded, despite the error messages. My version of git is 1.7.1.86.g0e460. Here is what happened (I force-pushed a single branch): Counting objects: 270, done. Delta compression using up to 8 threads. Compressing objects: 100% (71/71), done. Writing objects: 100% (184/184), 151.33 KiB, done. Total 184 (delta 157), reused 134 (delta 113) Auto packing the repository for optimum performance. fatal: protocol error: bad line length character: Remo error: error in sideband demultiplexer To git@xxxxxxxxxx:bjorng/otp.git + 7651a63...874192d bg/nif_error -> bg/nif_error (forced update) error: failed to push some refs to 'git@xxxxxxxxxx:bjorng/otp.git' -- Björn Gustavsson, Erlang/OTP, Ericsson AB -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html