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

how to rewalk the commit list after rename detection

From
DZDon Zickus <dzickus@redhat.com>
Date
Jun 23, 2008, 15:38 UTC
Message-ID
<20080623153814.GD15773@redhat.com>

I am trying to find a way to handle a situation where I am looking for a change in a particular file, but the filename is old and has since been renamed.

Processing the commit list internally (using init_revisions, setup_revisions, get_revision), I can easily find the rename of the file, but that is usually the start of the walk for that file (as it was just deleted for the rename). I do not know how to re-walk the commits list armed with the new file name.

I tried rerunning the same commands as above (init_revisions, setup_revisions, get_revision) but that commit list is empty for some reason (I assume the UNINTERESTING flag is never un-set??).

For example, if I have a backported patch for the upstream kernel in say the arch/i386 directory. I want to check to see if it is upstream. I wouldn't be able to do that because arch/i386 was renamed to arch/x86. Unless of course the patch matches identically upstream (in which case git-cherry works fine), but that isn't always the case (usually it is a combination of a couple of patches).

Anyone have some thoughts if this is possible?

Cheers, Don

Next: Alex Riesen
Message 1 of 3 in “how to rewalk the commit list after rename detection”
  1. Don ZickusJun 23, 2008
  2. Alex RiesenJun 25, 2008
  3. Jakub NarebskiJun 25, 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.