From: Marco Roeland <marco.roeland@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: segfault bug in internal git grep from next (fixed)
Date: Thu, 4 May 2006 10:44:18 +0200 [thread overview]
Message-ID: <20060504084418.GA10195@fiberbit.xs4all.nl> (raw)
In-Reply-To: <20060503083229.GA15579@fiberbit.xs4all.nl>
On Wednesday May 3rd 2006 Marco Roeland wrote:
> I'm using the next branch as of commit 6a40327d242dac9f85c6d63c94d537b45ba86e89
>
> A segfault occurs in using the new builtin grep when using it on a
> binary file, so no regular \n endings.
Fixed by Junio in commit 7ed36f56e33bd838d06521a37a916516397e9e8b.
I really use git grep a lot. It is very powerful, and the builtin version
makes even more possible. Thanks very much,
--
Marco Roeland
prev parent reply other threads:[~2006-05-04 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 8:32 segfault bug in internal git grep from next Marco Roeland
2006-05-04 8:44 ` Marco Roeland [this message]
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=20060504084418.GA10195@fiberbit.xs4all.nl \
--to=marco.roeland@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;
as well as URLs for NNTP newsgroup(s).