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 I tried t= o push to.
> The git daemon is very simple; see Documentation/technical/pack-protoco=
l.txt
> Basically it runs one of a number of helpers and dumps its output over
> the wire. For example, one helper is 'git receive-pack', used to
> handle push requests.
>=20
>[...]
>=20
> That is, it captures stderr from the child and writes it to the
> daemon=E2=80=99s log. All you have to do is figure out where to send t=
his
> output instead, and we=E2=80=99ll be done.
>=20
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 rem=
ote
URI? E.g. at least warning ("you are trying to push to read-only reposito=
ry").
--=20
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
signature.asc
Description: OpenPGP digital signature
