Git development
 help / color / mirror / Atom feed
From: Peter Kleiweg <pkleiweg@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: old but persistent problem: bad line length character
Date: Wed, 8 Jun 2011 00:32:31 +0200	[thread overview]
Message-ID: <alpine.DEB.1.10.1106072337500.11389@localhost> (raw)
In-Reply-To: <20110607180624.GA23752@sigill.intra.peff.net>

Jeff King schreef op de 7e dag van de zomermaand van het jaar 2011:

> On Tue, Jun 07, 2011 at 06:33:07PM +0200, Peter Kleiweg wrote:
> 
> > How do bugs in Git get solved? I can't find an issue tracker. 
> 
> You send an email to the mailing list and people work on it. :)

Is that git@vger.kernel.org ?


> > I added some debug code in pkt-line.c, function 
> > packet_read_line(). This tells me that 'buffer' that is passed 
> > to packet_read_line() contains nothing but null characters, 
> > while 'size' is set to 1000.
> 
> Yeah, it's expecting data to be written into it. You need to see what
> packet_read_line reads into linelen via safe_read (which is also printed
> in the error message, so it looks from the above like it contains NULs).

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.





-- 
Peter Kleiweg
http://pkleiweg.home.xs4all.nl/

  reply	other threads:[~2011-06-07 22:45 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 [this message]
2011-06-08 14:56     ` Junio C Hamano
2011-06-08 17:33       ` Jakub Narebski
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=alpine.DEB.1.10.1106072337500.11389@localhost \
    --to=pkleiweg@xs4all.nl \
    --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