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

Re: git-rev-list: proper lazy reachability

From
Paul Mackerras <paulus@samba.org>
Date
May 31, 2005, 12:15 UTC
Message-ID
<17052.21846.816147.370354@cargo.ozlabs.ibm.com>
In-Reply-To
<Pine.LNX.4.58.0505301847120.1876@ppc970.osdl.org>
Linus Torvalds writes:
> Ok, I just made git-rev-list DTRT when you pass it a "beginning" and 
> "end", ie it does proper reachability analysis _without_ parsing the whole 
> set of commits.

I have made gitk use git-rev-list instead of git-rev-tree, but it still absorbs the whole of git-rev-list's output before drawing anything. I'd like to make it draw the commit graph and list incrementally as it gets the output from git-rev-list, but to do that I need to know whether git-rev-list could ever print a commit ID *after* one of its parents. If it never does that then I can restructure the code to do the drawing incrementally fairly easily.

Paul.
Previous: Jon SeymourNext: Linus Torvalds
Message 6 of 16 in “git-rev-list: proper lazy reachability”
  1. Linus TorvaldsMay 31, 2005
  2. Jon SeymourMay 31, 2005
  3. Linus TorvaldsMay 31, 2005
  4. Linus TorvaldsMay 31, 2005
  5. Jon SeymourJun 1, 2005
  6. Paul MackerrasMay 31, 2005
  7. Linus TorvaldsMay 31, 2005
  8. Linus TorvaldsMay 31, 2005
  9. Matthias UrlichsJun 1, 2005
  10. Junio C HamanoJun 4, 2005
  11. Thomas GlanzmannJun 4, 2005
  12. Linus TorvaldsJun 4, 2005
  13. Linus TorvaldsJun 4, 2005
  14. Junio C HamanoJun 4, 2005
  15. Petr BaudisJun 4, 2005
  16. Junio C HamanoJun 4, 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.