From: Francis Moreau <francis.moro@gmail.com>
Date: Sat, 29 Jan 2011 12:52:15 GMT
Subject: Re: Can't find the revelant commit with git-log
Message-ID: <m2sjwb6feo.fsf@gmail.com>
In-Reply-To: <4D433CA7.9060200@lsrfire.ath.cx>

René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:

> Am 26.01.2011 19:11, schrieb René Scharfe:
>> - Make git grep report non-matching path specs (new feature).
>
> This is a bit complicated because grep can work on files, index entries
> as well as versioned objects and supports wildcards,
> so it's not that easy to tell if a path spec matches something or is a
> rather typo.  But it's not impossible either, of course.

I don't understand this for the following use case:

   $ cd ~/linux-2.6/drivers/pci/
   $ git grep blacklist v2.6.27 -- drivers/pci/intel-iommu.c

From what you said, it sounds that git grep is actually searching the
string 'somewhere'. But where ?

Thanks
-- 
Francis