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

Re: Need help merging unrelated histories

From
RDRobert Dailey <rcdailey.lists@gmail.com>
Date
May 28, 2019, 13:35 UTC
Message-ID
<CAHd499BQO8E99Y4=T9V6xXDuDyHdqMJ_sQM4DTraAxLzKf+Z-Q@mail.gmail.com>
In-Reply-To
<87ftp3lqvw.fsf@igel.home>
On Fri, May 24, 2019 at 12:11 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
Show 9 quoted lines
>
> 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?

I unfortunately have little-to-no experience with low level plumbing commands. Could you provide an example of a series of commands to run? It will help me to figure out how to do it on my own for my specific use case. Thanks in advance.

Previous: Andreas SchwabNext: Robert Dailey
Message 5 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.