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

Re: FFmpeg considering GIT

From
Shawn O. Pearce <spearce@spearce.org>
Date
May 8, 2007, 04:19 UTC
Message-ID
<20070508041939.GK11311@spearce.org>
In-Reply-To
<17983.63329.314321.305860@cargo.ozlabs.ibm.com>
Paul Mackerras <paulus@samba.org> wrote:
Show 10 quoted lines
> Brett Schwarz writes:
> > As Shawn mentions below, he started using namespaces for git-gui. I
> > think gitk could benefit from that as well, along with a few other
> > changes.
> 
> Gitk ends up handling pretty significant amounts of data.  In
> particular the per-commit data can get to gigabytes, and processing it
> is pretty cpu-intensive.  I did try using namespaces for the
> per-commit data but I found that the performance hit to be more than I
> was willing to tolerate.

If that is the case then an obvious direction is to start using C for the actual Git operations/datastore and Tcl/Tk for the basic UI layout and event handlers.

If we go down that path for gitk then I may wind up doing the same for git-gui. Because gitk would require the tcl/tk heders and libraries at that point, so also requiring them for git-gui wouldn't be too unreasonable.

But fortunately git-gui doesn't have to deal with gigabytes of data; I'm only really looking at the "dirty" stuff, or at worst, the blame for an entire file.

-- 
Shawn.
Previous: Paul MackerrasNext: Johannes Schindelin
Message 3 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.