Re: Fwd: Re: git send-pack: protocol error: bad band #50

2013-04-14 Thread Jeff King
On Sat, Apr 13, 2013 at 12:03:15PM +0100, João Joyce wrote: > I have tried to remove and recreate my git folder and remove some > files to get more logs. Here they are: Your output looks quite odd. > packet: push< > capabilities^{}\0 report-statu

Fwd: Re: git send-pack: protocol error: bad band #50

2013-04-13 Thread João Joyce
push some files to a server with git push. I have >> configured the server to push the files: >> git remote set-url test ssh://u...@location.com:2200/fullpath/ >> >> but I am getting the following error: >> git send-pack: protocol error: bad band #50 >> fatal: Th

Re: git send-pack: protocol error: bad band #50

2013-04-11 Thread João Joyce
test ssh://u...@location.com:2200/fullpath/ but I am getting the following error: git send-pack: protocol error: bad band #50 fatal: The remote end hung up unexpectedly That means that where git expected to read a binary sideband number, it instead received the byte \x32 (ASC

Re: git send-pack: protocol error: bad band #50

2013-04-11 Thread Jonathan Nieder
com:2200/fullpath/ > > but I am getting the following error: > git send-pack: protocol error: bad band #50 > fatal: The remote end hung up unexpectedly That means that where git expected to read a binary sideband number, it instead received the byte \x32 (ASCII '2'). Withou

Re: git send-pack: protocol error: bad band #50

2013-04-11 Thread Konstantin Khomoutov
On Thu, 11 Apr 2013 07:49:44 +0100 João Joyce wrote: [...] > but I am getting the following error: > git send-pack: protocol error: bad band #50 > fatal: The remote end hung up unexpectedly > > It seems that something is failing on the remote side but I can't >

git send-pack: protocol error: bad band #50

2013-04-11 Thread João Joyce
h://u...@location.com:2200/fullpath/ but I am getting the following error: git send-pack: protocol error: bad band #50 fatal: The remote end hung up unexpectedly It seems that something is failing on the remote side but I can't find any reference to this protocol error. Does anyone know ho