git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Lear <rael@zopyra.com>
To: git@vger.kernel.org
Subject: Meaning of "fatal: protocol error: bad line length character"?
Date: Sat, 20 Jan 2007 06:04:57 -0600	[thread overview]
Message-ID: <17842.1385.366750.915767@lisa.zopyra.com> (raw)

[Many thanks to Junio for explaining in generous detail how to think
properly about branches in git's distributed model.]

We are making progress in our conversion to git, but one of our
developers, on pushing into our company repo, has encountered this
error:

% git push
updating 'refs/heads/master'
  from 6b421066e842203e383e1dc466c1cdef10de56b1
  to   2a8e554ae0c99d44988690c9fce693b3f5f128fa
Generating pack...
Done counting 61 objects.
Result has 32 objects.
Deltifying 32 objects.
 100% (32/32) done
Writing 32 objects.
 100% (32/32) done
Total 32, written 32 (delta 18), reused 0 (delta 0)
Unpacking 32 objects
fatal: protocol error: bad line length character

The notion of fatality led him to think, quite plausibly, that
something very bad had happened with his push.  However, we can find
no evidence that anything bad really did happen.

I did read through the code, and pkt-line.c seems to be the origin of
this, and it does seem to short-circuit the read of the packet if this
error is encountered.  Of course, I have no idea what this really
means...

Could someone please explain what this error means, and how to deal
with it?

Thank you.


Bill

             reply	other threads:[~2007-01-20 12:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20 12:04 Bill Lear [this message]
2007-01-20 19:24 ` Meaning of "fatal: protocol error: bad line length character"? 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
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=17842.1385.366750.915767@lisa.zopyra.com \
    --to=rael@zopyra.com \
    --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).