From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Peter Kleiweg <pkleiweg@xs4all.nl>, git@vger.kernel.org
Subject: Re: old but persistent problem: bad line length character
Date: Wed, 08 Jun 2011 10:33:20 -0700 (PDT) [thread overview]
Message-ID: <m3d3iodya5.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vpqmo2wy7.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Peter Kleiweg <pkleiweg@xs4all.nl> writes:
>
> > I made it read some more than 4 bytes. And this is what I get:
> >
> > {27}]0;github git-receive-pack 'pebbe/Gabmap.git'{7}
> >
> > Ah, I see! I have a wrapper set-up around ssh that sets the
> > window title of the shell to the ssh command argument. That is
> > what messes things up!
> >
> > OK. Fixed now.
>
> That does not explain why you earlier said 1.4.4.4 works and more recent
> versions do not, though.
>From my #git channel logs:
Jun 03 19:09:42 <ShadeHawk> Hmmm... for a while I had transient (i.e. fixed now) error
when fetching from git.kernel.org repositories
Jun 03 19:09:50 <ShadeHawk> $ git fetch origin
Jun 03 19:09:59 <ShadeHawk> fatal: protocol error: bad line length character: git:
Jun 03 19:10:24 <ShadeHawk> but when I wanted to debug it (with GIT_TRACE_PACKET=2),
it was already fixed ;-P
$ git version
git version 1.7.5
It might be not related with issue that Peter encountered, though.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-06-08 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 16:33 old but persistent problem: bad line length character Peter Kleiweg
2011-06-07 18:06 ` Jeff King
2011-06-07 22:32 ` Peter Kleiweg
2011-06-08 14:56 ` Junio C Hamano
2011-06-08 17:33 ` Jakub Narebski [this message]
2011-06-08 18:33 ` Peter Kleiweg
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=m3d3iodya5.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pkleiweg@xs4all.nl \
/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).