From: Bill Lear <rael@zopyra.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Meaning of "fatal: protocol error: bad line length character"?
Date: Mon, 22 Jan 2007 13:55:25 -0600 [thread overview]
Message-ID: <17845.5805.290668.552757@lisa.zopyra.com> (raw)
In-Reply-To: <7vy7nusv52.fsf@assigned-by-dhcp.cox.net>
On Monday, January 22, 2007 at 11:45:29 (-0800) Junio C Hamano writes:
>Bill Lear <rael@zopyra.com> writes:
>
>> He has an active update hook in his public repo, to send notices to
>> his collaborators when his work is ready for them to pull, but we
>> looked through it and don't see any printing to stdout.
>
>Just a hunch.
>
>Does the bash start-up sequence for the user emit something to
>stdout?
Not that I can see. I logged into his machine, su root, su - <his id>,
and nothing but a prompt came up.
>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.
Thank you.
Bill
next prev parent reply other threads:[~2007-01-22 19:55 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 [this message]
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=17845.5805.290668.552757@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).