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

Re: [PATCH] fast-export: ensure we traverse commits in topological order

From
Jeff King <peff@peff.net>
Date
Feb 11, 2009, 13:56 UTC
Message-ID
<20090211135640.GA19600@coredump.intra.peff.net>
In-Reply-To
<e2b179460902110248m8055b3amdebcfc550438cff2@mail.gmail.com>
On Wed, Feb 11, 2009 at 10:48:18AM +0000, Mike Ralphson wrote:
Show 8 quoted lines
> > On Tue, 10 Feb 2009, newren@gmail.com wrote:
> > fast-export will only list as parents those commits which have already
> > been traversed (making it appear as if merges have been squashed if not
> > all parents have been traversed).  To avoid this silent squashing of
> > merge commits, we request commits in topological order.
> 
> Any comparative timings? We don't need to rename this to 'git
> reasonably-speedy-export'? 8-)
Hmm.
In git.git:
  $ time git fast-export --all --signed-tags=strip >/dev/null
  real    1m6.013s
  user    1m3.840s
  sys     0m2.140s
  $ time git fast-export --all --signed-tags=strip --topo-order >/dev/null
  real    0m49.018s
  user    0m47.987s
  sys     0m0.888s

I certainly didn't expect it to be _faster_. More efficient use of the delta cache, maybe?

-Peff
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 6 of 10 in “Add new testcase to show that fast-export can squash merge commits”
  1. Add new testcase to show that fast-export can squash merge commitsnewren@gmail.com, Feb 11, 2009
  2. fast-export: ensure we traverse commits in topological ordernewren@gmail.com, Feb 11, 2009
  3. Johannes SchindelinFeb 11, 2009
  4. Mike RalphsonFeb 11, 2009
  5. Johannes SchindelinFeb 11, 2009
  6. Jeff KingFeb 11, 2009
  7. Johannes SchindelinFeb 11, 2009
  8. Jeff KingFeb 11, 2009
  9. Elijah NewrenFeb 11, 2009
  10. Jeff KingFeb 11, 2009

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.