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

Re: Track git blame through two unrelated histories

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2023, 18:35 UTC
Message-ID
<xmqqwn3pai2d.fsf@gitster.g>
In-Reply-To
<CAAo-ADZBBRxSROeAwrA9o30Etf3QQhLCaWQJtVsChVwT-AbgTg@mail.gmail.com>
Ilia Pozhilov <ilyapoz@gmail.com> writes:
Show 9 quoted lines
> So let's say I add two remotes and fetch all the commits, but they
> look like this:
>
> A->B-> .... . . . -> Z    history1
>
> 1 -> 2 -> ..... -> 0 history2
>
> and file contents in commits Z and 1 are exactly the same, but the
> commits themselves are completely unrelated for git.

You mean you want to pretend that history "2 -> ... -> 0" was built on top of Z? Here I am assuming that time flows from left to right in the picture.

If so, you should be able to graft the histories together, perhaps?
Totally untested but something like 
	$ git replace --graft 1 Z

based on my reading of "git help replace" should allow you to pretend that Z happened immediately before 1.

Previous: Ilia PozhilovNext: Ilia Pozhilov
Message 2 of 4 in “Track git blame through two unrelated histories”
  1. Ilia PozhilovMar 9, 2023
  2. Junio C HamanoMar 9, 2023
  3. Ilia PozhilovMar 13, 2023
  4. Ilia PozhilovMar 13, 2023

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.