git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Meaning of "fatal: protocol error: bad line length character"?

From
Bill Lear <rael@zopyra.com>
Date
Jan 20, 2007, 12:04 UTC
Message-ID
<17842.1385.366750.915767@lisa.zopyra.com>

[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
Next: Junio C Hamano
Message 1 of 17 in “Meaning of "fatal: protocol error: bad line length character"?”
  1. Bill LearJan 20, 2007
  2. Junio C HamanoJan 20, 2007
  3. Junio C HamanoJan 20, 2007
  4. Bill LearJan 20, 2007
  5. Jakub NarebskiJan 20, 2007
  6. Junio C HamanoJan 20, 2007
  7. Junio C HamanoJan 20, 2007
  8. Shawn O. PearceJan 20, 2007
  9. Junio C HamanoJan 22, 2007
  10. Bill LearJan 22, 2007
  11. Junio C HamanoJan 22, 2007
  12. Bill LearJan 22, 2007
  13. Bill LearJan 22, 2007
  14. Junio C HamanoJan 22, 2007
  15. Han-Wen NienhuysJan 23, 2007
  16. Junio C HamanoJan 23, 2007
  17. Han-Wen NienhuysJan 23, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.