From: Michael J Gruber <git@drmicha.warpmail.net>
To: Mark Constable <markc@renta.net>
Cc: git@vger.kernel.org
Subject: Re: bad line length character: fata
Date: Mon, 17 May 2010 10:16:01 +0200 [thread overview]
Message-ID: <4BF0FB41.5000500@drmicha.warpmail.net> (raw)
In-Reply-To: <loom.20100516T095148-64@post.gmane.org>
Mark Constable venit, vidit, dixit 16.05.2010 09:53:
> What does this error message indicate when doing a git pull?
>
> fatal: protocol error: bad line length character: fata
>
> Git v1.7.1 both ends.
This is funny. Git tries to read a 4 digit (hex) line length according
to the git protocol, and what it got from the remote end apparently was
a "fatal..." at a place where there usually is no textual error report.
Can you reproduce this and describe the circumstances? For example, what
is the transport (ssh, http), what are the surrounding messages, does it
happen for every client?
Michael
prev parent reply other threads:[~2010-05-17 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 7:53 bad line length character: fata Mark Constable
2010-05-17 8:16 ` Michael J Gruber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF0FB41.5000500@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=markc@renta.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).