From: Bill Lear <rael@zopyra.com>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Meaning of "fatal: protocol error: bad line length character"?
Date: Mon, 22 Jan 2007 16:16:05 -0600 [thread overview]
Message-ID: <17845.14245.559835.112658@lisa.zopyra.com> (raw)
In-Reply-To: <17845.5805.290668.552757@lisa.zopyra.com>
On Monday, January 22, 2007 at 13:55:25 (-0600) Bill Lear writes:
>...
>>The attached patch on the local side (i.e. the one that pushes)
>>dumps "garbage" you are getting on the line from the remote
>>side, to help diagnosing the problem. ...
>
>I have asked the developer to install this and hopefully we'll
>get some feedback soon.
Looks like it is our developer's fault after all.
% git push
[...]
Unpacking 7 objects
100% (7/7) done
error: protocol error: bad line length character
<<<<<
Unknown command: "#alias"
refs/heads/tau_mt_1: 0a5a7ac9b81a90500b9c9c44a22793890513cd5a -> 3d0c74c15953ad5bc6a71eefa623933163c4f05f
[...]
The problem is that his mailer is putting out:
Unknown command: "#alias"
when it gets to the mail command at the bottom of the update hook. So,
he's got a bad line in his .mailrc file.
I do think that some augmentation of the error output is in order,
either as previously posted, or something fancier. It would be even
better if this sort of thing did not trip up git, though perhaps
I don't understand enough of how the update hook and git interact.
Bill
next prev parent reply other threads:[~2007-01-22 22:16 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 [this message]
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=17845.14245.559835.112658@lisa.zopyra.com \
--to=rael@zopyra.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).