On Fri, Sep 04, 2015 at 12:04:38AM +0000, Rustad, Mark D wrote: > You can see that git grep missed the line in ixgbe_x550.c that had two hits > on the string. > > This was with git 2.1.0 in Fedora 21. I use git grep a lot and never > noticed a problem before. I just updated my Fedora 21 system > yesterday, so I have to figure that has something to do with it. I > checked and git didn't get updated, so I figure it must be a library > that is really broken. > > I see in my update log that pcre was updated to: > > pcre.x86_64 0:8.35-12.fc21 > pcre-devel.x86_64 0:8.35-12.fc21 > > Yet the grep command is unaffected.
I don't think "git grep" should be using pcre unless you specified "-P" on the command line (which might be an interesting experiment, to see if it improves the result). It shouldn't be affected by your working tree state. "git grep" without arguments searches the working tree, just like grep. It might omit a file that is not tracked, but given that the missing line is from a file which _does_ have other results, that's clearly not the problem. Is it possible that git _is_ producing the hit, but it is getting eaten by the pager or something like that? Does "git --no-pager grep enter_lplu" produce the same results? I don't think there have been any git bugs in this area for quite a while. In your position I'd try building from source to see if a freshly built version has the same problem. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
