public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Bernt Hansen <bernt@norang•ca>
To: Jeff King <peff@peff•net>
Cc: Markus Trippelsdorf <markus@trippelsdorf•de>,
	"Richard W.M. Jones" <rjones@redhat•com>,
	meyering@redhat•com, git@vger•kernel.org
Subject: Re: general protection faults with "git grep" version 1.7.7.1
Date: Tue, 25 Oct 2011 07:11:31 -0400	[thread overview]
Message-ID: <87zkgpxr4s.fsf@norang.ca> (raw)
In-Reply-To: <20111025055310.GB1902@sigill.intra.peff.net> (Jeff King's message of "Mon, 24 Oct 2011 22:53:11 -0700")

Jeff King <peff@peff•net> writes:

> On Mon, Oct 24, 2011 at 08:00:15PM -0400, Bernt Hansen wrote:
>
>> I updated from an old commit 2883969 (Sync with maint, 2011-10-15)
>> to origin/master 10b2a48 (Merge branch 'maint', 2011-10-23) today and
>> promptly got segfaults on git status in my org-mode repository.
>> 
>> Going back to the old commit makes it work again.
>> 
>> Git bisect identifies the following commit as the problem:
>> 
>> [2548183badb98d62079beea62f9d2e1f47e99902] fix phantom untracked files when core.ignorecase is set
>
> I think this is a separate problem. See this thread and patch:
>
>   http://thread.gmane.org/gmane.comp.version-control.git/184094/focus=184148

Thanks,

I'll look at that thread.

-Bernt

  reply	other threads:[~2011-10-25 11:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 20:11 general protection faults with "git grep" version 1.7.7.1 Markus Trippelsdorf
2011-10-24 21:49 ` Richard W.M. Jones
2011-10-24 22:58   ` Markus Trippelsdorf
2011-10-25  0:00     ` Bernt Hansen
2011-10-25  5:53       ` Jeff King
2011-10-25 11:11         ` Bernt Hansen [this message]
2011-10-25 13:50   ` Thomas Rast
2011-10-25 15:17     ` Jim Meyering
2011-10-25 15:32       ` Markus Trippelsdorf
2011-10-25 16:00       ` Thomas Rast
2011-10-25 16:07         ` Thomas Rast
2011-10-25 16:37         ` Jim Meyering
2011-10-25 16:54           ` Thomas Rast
2011-10-25 20:24             ` Jim Meyering
2011-10-25 15:37     ` Jeff King

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=87zkgpxr4s.fsf@norang.ca \
    --to=bernt@norang$(echo .)ca \
    --cc=git@vger$(echo .)kernel.org \
    --cc=markus@trippelsdorf$(echo .)de \
    --cc=meyering@redhat$(echo .)com \
    --cc=peff@peff$(echo .)net \
    --cc=rjones@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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