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

Re: Need help merging unrelated histories

From
Andreas Schwab <schwab@linux-m68k.org>
Date
May 24, 2019, 17:10 UTC
Message-ID
<87ftp3lqvw.fsf@igel.home>
In-Reply-To
<CAHd499AidrL4jCG_WytPJF9yHfJJJvWJ5fpjKN6sGBY5Weu8Hg@mail.gmail.com>
On Mai 24 2019, Robert Dailey <rcdailey.lists@gmail.com> wrote:
> Can anyone provide some advice on how to properly restructure this
> repository to create some ancestry, as if all along a `master` existed
> and all release branches were based on this in a linear fashion?

How about using git replace --graft, then git filter-branch to make it permanent?

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."
Previous: Ævar Arnfjörð BjarmasonNext: Robert Dailey
Message 4 of 7 in “Need help merging unrelated histories”
  1. Robert DaileyMay 24, 2019
  2. Robert DaileyMay 24, 2019
  3. Ævar Arnfjörð BjarmasonMay 24, 2019
  4. Andreas SchwabMay 24, 2019
  5. Robert DaileyMay 28, 2019
  6. Robert DaileyMay 28, 2019
  7. Philip OakleyMay 29, 2019

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.