Re: Bug in git log -S

From: Sam Clymer <clymersam@gmail.com>
Date: May 13, 2024, 18:58 UTC
Message-ID: <8B9537F6-A76A-4CF8-9EE4-2CC3C98D5784@gmail.com>
In-Reply-To: <8bfa50e3-996a-407b-9c02-a9fcacfebc4f@kdbg.org>

There does seem to be a bug on my end. I am searching for “net8.0-windows” and it’s not finding an instance where it’s added. It is not a line of code that is moved around it is purely added so I think there is indeed something wrong with git log -S.

Please let me know if I can be of help in resolving this.

Many thanks, Sam Clymer

Show 19 quoted lines

> On May 13, 2024, at 1:55 AM, Johannes Sixt <j6t@kdbg.org> wrote:
> 
> Am 13.05.24 um 03:40 schrieb Sam Clymer:
>> There is a bug in git log -S where it doesn’t find every instance of
>> the search string.
> -S does not search for *every* instance of the search string, but only
> for those that change the number of occurrences of the search string in
> the repository.
> 
> For example, if you have a commit that only moves a line of code around
> that contains the search string, i.e., it removes the search string in
> one place and adds it in another places, this commit will not be listed,
> because it does not change the number of times that the search string
> occurs in the repository.
> 
> There is also -G. Maybe it is what you are looking for?
> 
> -- Hannes
>