On Fri, Nov 18, 2011 at 2:49 PM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: > Am 11/18/2011 11:54, schrieb Bart van den Burg: >> I somehow managed to break my GIT repo. Whenever I try to clone or fetch >> from a clean local repo, I get an error. >> >> I'm able to go back on the server, to the very last commit where >> everything works, but as soon as I make a change locally and push it, it >> breaks again. > ... >> $ git clone git@xxxxxxxxxxxxxxxx:/home/git/shifter_rai > ... >> Receiving objects: 100% (9557/9557), 2.85 MiB | 1.06 MiB/s, done. > ... >> $ git push >> Counting objects: 4, done. >> Delta compression using up to 4 threads. >> Compressing objects: 100% (2/2), done. >> Writing objects: 100% (3/3), 271 bytes, done. >> Total 3 (delta 1), reused 0 (delta 0) >> To git@xxxxxxxxxxxxxxxx:/home/git/shifter_rai >> cc5693a..85d1ee9 master -> master > > It looks like you are pushing via git protocol from Windows > (Git-for-Windows). This is known to dead-lock in most cases, and even > though it did not here, I would not be surprised if it had other issues. > > Do not do it. Push via ssh instead. > Does it? Doesn't the "To git@xxxxxxxxxxxxxxxx:/home/git/shifter_rai" line suggests ssh? -- 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