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

Re: Blaming diffs

From
Christian Couder <chriscool@tuxfamily.org>
Date
Sep 17, 2007, 04:59 UTC
Message-ID
<200709170659.15655.chriscool@tuxfamily.org>
In-Reply-To
<20070916163829.GA6679@glandium.org>
Le dimanche 16 septembre 2007, Mike Hommey a écrit :
> Hi,
>
> It seems to me there is no tool to "blame diffs", i.e. something to know
> what commit(s) is(are) responsible for a set of changes.

I don't know if that's what you are looking for but perhaps you could use "git bisect run". You just need to pass it a script that returns 1 when it finds the changes and 0 otherwise. (See git-bisect man page.)

Sometimes ago I sent a patch that would allow "!" after "git bisect run", but it seems to have been forgotten. This patch makes it possible to use:

git bisect run ! grep some_stuff file1 file2...

This would give you the commit where some_stuff was introduced in file1 or file2...

Regards, Christian.

Previous: Mike HommeyNext: Shawn O. Pearce
Message 4 of 7 in “Blaming diffs”
  1. Mike HommeySep 16, 2007
  2. Frank LichtenheldSep 16, 2007
  3. Mike HommeySep 16, 2007
  4. Christian CouderSep 17, 2007
  5. Shawn O. PearceSep 17, 2007
  6. Christian CouderSep 17, 2007
  7. Junio C HamanoSep 17, 2007

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.