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

Re: [RFH] Finding all commits that touch the same files as a specific commit

From
SRSverre Rabbelier <alturin@gmail.com>
Date
Jul 14, 2008, 14:30 UTC
Message-ID
<bd6139dc0807140730o2cdc64d0m28a83dfa72d1496b@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0807141311520.8950@racer>

On Mon, Jul 14, 2008 at 2:13 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> IMO following the file renames/code moves precisely is really worth the
> time it takes to calculate.  Otherwise, the statistics will not reflect
> what was going on in the project, right?

Ah, I did not mean to imply that it is not worth the time it takes to calculate, more that I do not know how to implement it that way. Of course if someone has the time/motivation to do so I would very much make use of it, but I do not have time to do so myself (at least not until after GSoC). I can have GitStats just ignore the subtree merge cases (and say that it is not beyond the scope of my project to take such into account) and have a working program by the end of GSoC. But if I spend time on getting this to work instead I might end up with a program that does follow sub-tree merges but is only half-done, and as such probably won't receive a "OK" grade. So, yes, I would very much like to see this, but no time to look into doing so myself until after GSoC.

-- 
Cheers,

Sverre Rabbelier
Previous: Johannes Schindelin
Message 7 of 7 in “[RFH] Finding all commits that touch the same files as a specific commit”
  1. Sverre RabbelierJul 12, 2008
  2. Junio C HamanoJul 13, 2008
  3. Sverre RabbelierJul 13, 2008
  4. Johannes SchindelinJul 13, 2008
  5. Sverre RabbelierJul 14, 2008
  6. Johannes SchindelinJul 14, 2008
  7. Sverre RabbelierJul 14, 2008

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.