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

Re: scan entire repo for changes to file

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 12, 2010, 01:44 UTC
Message-ID
<20101112014434.GA10679@burratino>
In-Reply-To
<AANLkTi=uKhrvAS6ApnmCZnfbFboYU77rNcKDpaSBn1id@mail.gmail.com>
Martin von Zweigbergk wrote:
> On Thu, Nov 11, 2010 at 8:28 PM, Neal Kreitzinger <neal@rsss.com> wrote:
Show 7 quoted lines
>> Is there a way to scan my entire repo (many unmerged branches) for any
>> changes to a file?
>> e.g.
>> $ git log * -- somepath/myblob
>> would return all commits in the repo that changed myblob.
>
> Might replacing '*' by '--all' give you what are looking for?

Probably with --full-history if you want to know what happened on historic branches, too.

Previous: Martin von ZweigbergkNext: Junio C Hamano
Message 3 of 6 in “scan entire repo for changes to file”
  1. Neal KreitzingerNov 12, 2010
  2. Martin von ZweigbergkNov 12, 2010
  3. Jonathan NiederNov 12, 2010
  4. Junio C HamanoNov 16, 2010
  5. Jonathan NiederNov 16, 2010
  6. Neal KreitzingerNov 18, 2010

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.