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

Re: gitk and git-gui, was Re: FFmpeg considering GIT

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
May 8, 2007, 15:33 UTC
Message-ID
<alpine.LFD.0.98.0705080830380.3974@woody.linux-foundation.org>
In-Reply-To
<Pine.LNX.4.64.0705081311550.4167@racer.site>
On Tue, 8 May 2007, Johannes Schindelin wrote:
> 
> It might be a much better idea to write something a la git-fetch--tool, 
> which is a helper in C (thus very fast and memory efficient), outputting 
> easily parseable data. 

Well, we actually do have that. "git log" (or "git-rev-list") really does all the heavy lifting. The reason you can do things like "gitk --merge" is not because gitk itself has _any_ idea about anything, but because it just passes the arguments down to git-rev-list (and hopefully soon git log), which really does all the complex stuff.

But gitk still ends up having a big memory footpring, simply because if you get the data for a few hundred thousand commits (with commit messages etc), and have to keep track of the relationships between them, you are going to easily use hundreds of megs of memory.

		Linus
Previous: Johannes Schindelin
Message 5 of 5 in “Re: FFmpeg considering GIT”
  1. Brett SchwarzMay 8, 2007
  2. Paul MackerrasMay 8, 2007
  3. Shawn O. PearceMay 8, 2007
  4. gitk and git-gui, was Re: FFmpeg considering GITJohannes Schindelin, May 8, 2007
  5. Linus TorvaldsMay 8, 2007

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.