From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: Meaning of "fatal: protocol error: bad line length character"?
Date: Tue, 23 Jan 2007 01:14:22 +0100 [thread overview]
Message-ID: <45B5535E.2000808@xs4all.nl> (raw)
In-Reply-To: <7vk5zh7b7d.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano escreveu:
> I've seen this "bad line length character" mentioned in #git and
> on this list but nobody seems to have hunted down what this is.
>
> http://www.gelato.unsw.edu.au/archives/git/0603/17807.html
>
> is another (Google finds some others for the error message on
> xcb list but that is about fetch-pack which is totally different
> codepath).
if you need another example where this is happening, the anongit
repo for lilypond seems to have gotten in this state as well,
[hanwen@haring tmp]$ git clone git://git.sv.gnu.org/lilypond.git
Initialized empty Git repository in /tmp/lilypond/.git/
fatal: protocol error: bad line length character
fetch-pack from 'git://git.sv.gnu.org/lilypond.git' failed.
pushing/pulling over ssh+git and http still work.
(git 1.5.0rc2, not sure what git.sv.gnu.org is running)
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2007-01-23 0:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 12:04 Meaning of "fatal: protocol error: bad line length character"? Bill Lear
2007-01-20 19:24 ` Junio C Hamano
2007-01-20 19:33 ` Junio C Hamano
2007-01-20 19:54 ` Bill Lear
2007-01-20 20:07 ` Jakub Narebski
2007-01-20 20:20 ` Junio C Hamano
2007-01-20 20:42 ` Junio C Hamano
2007-01-20 21:37 ` Shawn O. Pearce
2007-01-22 20:15 ` Junio C Hamano
2007-01-22 18:58 ` Bill Lear
2007-01-22 19:45 ` Junio C Hamano
2007-01-22 19:55 ` Bill Lear
2007-01-22 22:16 ` Bill Lear
2007-01-22 22:33 ` Junio C Hamano
2007-01-23 0:14 ` Han-Wen Nienhuys [this message]
2007-01-23 0:44 ` Junio C Hamano
2007-01-23 0:53 ` Han-Wen Nienhuys
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=45B5535E.2000808@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=git@vger.kernel.org \
/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).