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

Re: Merging repositories and their histories

From
Alex Riesen <raa.lkml@gmail.com>
Date
Aug 18, 2008, 17:35 UTC
Message-ID
<20080818173511.GC6014@blimp.local>
In-Reply-To
<19035412.post@talk.nabble.com>
Peter Waller, Mon, Aug 18, 2008 18:46:14 +0200:
Show 6 quoted lines
> 
> I have three repositories, A, B and C. I wish to bring them together to only
> one repository (.), where they are in a directory called ./Archive, so..
> ./Archive/{A,B,C}. Then I plan at a later date to move files arbitrarily
> from ./Archive/{A/B/C}/Something and into ./Something{A/B/C}. (A lame
> example, but illustrates what I want to do).

If this transition is meant to be persistent (IOW, the A, B and C stop existing as repos on their own) you can rewrite their histories to be in the directories (with git filter-branch) and just merge them in one. Then the histories will look like as if they have never grown separately.

Previous: Peter WallerNext: Peter Waller
Message 2 of 8 in “Merging repositories and their histories”
  1. Peter WallerAug 18, 2008
  2. Alex RiesenAug 18, 2008
  3. Peter WallerAug 18, 2008
  4. Marcus GriepAug 21, 2008
  5. Peter WallerAug 21, 2008
  6. Alex RiesenAug 22, 2008
  7. Alex RiesenAug 18, 2008
  8. Peter WallerAug 18, 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.