severity 552121 important
tags 552121 + patch
quit
Eugene V. Lyubimkin wrote:
$ git push
fatal: The remote end hung up unexpectedly
Isn't helpful at all and made me think about server's problem.
Sad story: a rough fix for this has been available for months[1]
but I dropped the ball and
Eugene V. Lyubimkin wrote:
I am not familiar with git's code, so can't analyze much.
Instead, as the real cause was the fact that I set remote to read-only
address, can this be checked by client side by checking the scheme of remote
URI? E.g. at least warning (you are trying to push to
tags 552121 + upstream
retitle 552121 git daemon: The remote end hung up unexpectedly is not a
useful message
thanks
Hi Eugene,
Eugene V. Lyubimkin wrote:
$ git push
fatal: The remote end hung up unexpectedly
Isn't helpful at all and made me think about server's problem.
I assume you are
Jonathan Nieder wrote:
Eugene V. Lyubimkin wrote:
=20
$ git push
fatal: The remote end hung up unexpectedly
Isn't helpful at all and made me think about server's problem.
=20
I assume you are using git-daemon on the other end?
I can't say for sure, because I don't remember which repository
Package: git-core
Version: 1:1.6.5-1
Severity: normal
$ git push
fatal: The remote end hung up unexpectedly
Isn't helpful at all and made me think about server's problem.
Please print a graceful error message when the real error is trying to
push to read-only repository.
-- System
5 matches
Mail list logo
