git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug in git log -S

From
Johannes Sixt <j6t@kdbg.org>
Date
May 13, 2024, 21:01 UTC
Message-ID
<6d7ac19b-fede-4534-aee2-5c0cb20f955e@kdbg.org>
In-Reply-To
<8B9537F6-A76A-4CF8-9EE4-2CC3C98D5784@gmail.com>
Am 13.05.24 um 20:58 schrieb Sam Clymer:
> 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.

You would have to show more evidence for a bug before anything can happen. Start with showing the commands typed and their output, ideally you point at a commit history that shows the problem, etc. Otherwise, we can only say: "it works here".

-- Hannes
Previous: Sam ClymerNext: Jeff King
Message 4 of 5 in “Bug in git log -S”
  1. Sam ClymerMay 13, 2024
  2. Johannes SixtMay 13, 2024
  3. Sam ClymerMay 13, 2024
  4. Johannes SixtMay 13, 2024
  5. Jeff KingMay 15, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.