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

Re: git-rev-list --merge-order hangs

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jun 8, 2005, 07:22 UTC
Message-ID
<2cfc4032050608002258e58897@mail.gmail.com>
In-Reply-To
<42A69550.1030105@gorzow.mm.pl>
On 6/8/05, Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl> wrote:
Show 10 quoted lines
> I've got a Linux git tree with some merges and some other commits
> interwined.
> I want to print all my changes in merge order, so I do:
> 
> git-rev-list --pretty --merge-order v2.6.12-rc6-astorm1 ^v2.6.12-rc6
> 
> It prints the first 3 commits (linear), but then hangs, eating all
> available CPU.
> Without --merge-order it works fine, but obviously lists the commits by
> parent.

Can you git-rev-list >/dev/null without arguments, then do a git-rev-list --pretty --merge-order again and see it works any better?

If it still doesn't work, can you send me the output of:
        git-rev-list --parents v2.6.12-rc6-astorm1 ^v2.6.12-rc6 

I may then need to request a tarball of the related git objects so that I can reproduce the problem on my end, but I'll send you the list I need to see.

Regards,
jon.
Previous: Radoslaw SzkodzinskiNext: Jon Seymour
Message 2 of 5 in “git-rev-list --merge-order hangs”
  1. Radoslaw SzkodzinskiJun 8, 2005
  2. Jon SeymourJun 8, 2005
  3. Jon SeymourJun 8, 2005
  4. Jon SeymourJun 8, 2005
  5. Radoslaw SzkodzinskiJun 8, 2005

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.