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

Re: git-fast-export bug, commits emmitted in incorrect order causing parent data to be lost from commits turning essentially linear repo into "islands"

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 12, 2008, 12:45 UTC
Message-ID
<48511A85.9020200@viscovery.net>
In-Reply-To
<1213272962.6940.231.camel@gemini>
Yves Orton schrieb:
Show 5 quoted lines
> BTW, for the record this was needed because we are trying to merge
> multiple git repos into a single new git repo with each original repo
> mapped into a subdirectory of the new repo, and with commit trees merged
> in more or less the correct order (by date applied more or less). IOW we
> dont want to have multiple "root commits" that are later merged.

Try --date-order instead. It might work better for your task, and it still offers a topologically correct order.

-- Hannes
Previous: Yves OrtonNext: Michael J Gruber
Message 5 of 7 in “git-fast-export bug, commits emmitted in incorrect order causing parent data to be lost from commits turning essentially linear repo into "islands"”
  1. Yves OrtonJun 12, 2008
  2. Johannes SixtJun 12, 2008
  3. Yves OrtonJun 12, 2008
  4. Yves OrtonJun 12, 2008
  5. Johannes SixtJun 12, 2008
  6. Michael J GruberJun 12, 2008
  7. Philippe Bruhat (BooK)Jun 12, 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.