All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Segmentation fault in git read-tree
Date: Fri, 14 Mar 2008 14:24:27 -0400	[thread overview]
Message-ID: <200803141424.28034.lenb@kernel.org> (raw)
In-Reply-To: <7vskytuc55.fsf@gitster.siamese.dyndns.org>

confirmed fixed.

thanks guys, for the great support!

I'm pleased that I can (almost fearlessly) update git on a daily basis.
On the rare occasion I run into issues, you kill 'em quick.

-Len

[lenb@t61 acpi (test)]$ git merge test suspend
Already up-to-date with 5dceb6d3377c3cbd06f7b3282fec0e201273c302
Trying simple merge with c68a5009ab9938af22af668e0e2d646d2482c866
Merge made by octopus.
 arch/frv/kernel/pm.c            |    8 --
 arch/mips/au1000/common/power.c |   35 +-------
 arch/x86/kernel/apm_32.c        |   15 ---
 kernel/power/Kconfig            |   10 --
 kernel/power/Makefile           |    1 -
 kernel/power/pm.c               |  205 ---------------------------------------
 6 files changed, 1 insertions(+), 273 deletions(-)
 delete mode 100644 kernel/power/pm.c
[lenb@t61 acpi (test)]$ git version
git version 1.5.4.4.551.g1658

  reply	other threads:[~2008-03-14 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  3:59 Segmentation fault git read-tree Len Brown
2008-03-14  4:26 ` Linus Torvalds
2008-03-14  4:30   ` Linus Torvalds
2008-03-14  4:37   ` Segmentation fault in " Linus Torvalds
2008-03-14  4:44     ` Junio C Hamano
2008-03-14  4:48     ` Junio C Hamano
2008-03-14  5:07       ` Junio C Hamano
2008-03-14 18:24         ` Len Brown [this message]
2008-03-14 17:37       ` Linus Torvalds

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=200803141424.28034.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.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.