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

Following history of a copied file from another indirect branch

From
Joshua Jensen <jjensen@workspacewhiz.com>
Date
Oct 21, 2010, 18:47 UTC
Message-ID
<4CC08AA5.8070502@workspacewhiz.com>

It has become a necessity to copy a file from one long-lived branch to another. It is not possible to merge the branches at this time.

I would like to have 'git gui blame' follow the copy back through its original history, but I don't believe Git has metadata for storing this. Something along the lines of a 'followparent' in the commit object, for instance, would allow the revision walking code to wander the history down an alternate line.

By comparison, integrates work at a file level in Perforce. That means I can integrate a file from one branch to another, and parentage is stored such that I can follow the file back through its history.

Are there any facilities to do this now?
Thanks!
Josh
Next: Brian Gernhardt
Message 1 of 4 in “Following history of a copied file from another indirect branch”
  1. Joshua JensenOct 21, 2010
  2. Brian GernhardtOct 21, 2010
  3. Joshua JensenOct 21, 2010
  4. Johannes SixtOct 22, 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.