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

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

From
RSRadoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
Date
Jun 8, 2005, 15:28 UTC
Message-ID
<42A70E81.7090308@gorzow.mm.pl>
In-Reply-To
<2cfc4032050608020215152887@mail.gmail.com>
Jon Seymour wrote:
Show 12 quoted lines
>Actually, one case that I may not have considered properly is a commit
>near the head that has no parents.
>
>      git-rev-list --parents v2.6.12-rc6-astorm1 ^v2.6.12-rc6
>
>should tell you if this case exists. Ideally such a case should not
>occur, but that isn't a logical certainity, so I should handle it
>better than I currently do.
>
>Please let me know if this may explain your case. 
>  
>

This just threw tons of SHA1 hashes at me without complaining. I've also tried git-rev-list HEAD >/dev/null without any chage whatsoever.

The tree is not secret, You can try (very slow) rsync at: rsync://astralstorm.servegame.com/linux-2.6-astorm

Just update latest linux-2.6 with it to save time. (mine is up to commit 1d6757fbff5bc86e94e59ab0d7bdd7e71351d839)

AstralStorm
Previous: Jon Seymour
Message 5 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.