All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-pasky-0.6.3 && request for testing
Date: Fri, 22 Apr 2005 12:37:37 +0200	[thread overview]
Message-ID: <20050422103737.GC14565@pasky.ji.cz> (raw)
In-Reply-To: <20050422072437.GC8467@ip68-225-251-162.oc.oc.cox.net>

Dear diary, on Fri, Apr 22, 2005 at 09:24:37AM CEST, I got a letter
where "Barry K. Nathan" <barryn@pobox.com> told me that...
> On Fri, Apr 22, 2005 at 12:16:26AM -0700, Barry K. Nathan wrote:
> > With git-pasky 0.6.3, "git log" is unusable on my Mandrake 10.1 system.
> > Basically I get a neverending flood of these until I press 'q' to quit
> > less:
> [snip sed segmentation faults which happen with 0.6.3 but not 0.6.2]
> > I'm not sure if I have time tonight (or tomorrow) to troubleshoot this
> > further, but I'll see if I can.
> 
> I had sed-4.1.1-2mdk. I downloaded sed-4.1.4-2mdk (from Mandriva 2005
> Limited Edition) and updated to that, and the problem went away.
> 
> FWIW this is the second package I've had to update to the Mandriva 2005
> LE level (the first was mktemp). I don't mind however.

Duh, segfaulting sed! Could you please check which of the sed
invocations actually segfault for you?

Thanks,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

  reply	other threads:[~2005-04-22 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22  3:09 [ANNOUNCE] git-pasky-0.6.3 && request for testing Petr Baudis
2005-04-22  3:58 ` Steven Cole
2005-04-22  6:49 ` Greg KH
2005-04-22 23:05   ` Petr Baudis
2005-04-22 23:27     ` Linus Torvalds
2005-04-23  0:18       ` Linus Torvalds
2005-04-22  7:16 ` Barry K. Nathan
2005-04-22  7:24   ` Barry K. Nathan
2005-04-22 10:37     ` Petr Baudis [this message]
2005-04-23  5:12       ` Barry K. Nathan

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=20050422103737.GC14565@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=barryn@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.