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

Re: Why so much time in the kernel?

From
Jon Smirl <jonsmirl@gmail.com>
Date
Jun 16, 2006, 17:00 UTC
Message-ID
<9e4733910606161000t53328571u10a350eca894ccdc@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.64.0606160906250.5498@g5.osdl.org>

Is it a crazy idea to read the cvs files, compute an sha1 on each expanded delta and then write the delta straight into a pack file? Are the cvs and git delta formats the same? What about CVS's forward and reverse delta use? While this is going on, track the branches/changsets in memory and then finish up by writing these trees into the pack file too. This should take no more ram than cvsps needs currently.

This leaves the packfile is a non-optimal format but a repack should fix that, right?

-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Linus TorvaldsNext: Jakub Narebski
Message 5 of 11 in “Why so much time in the kernel?”
  1. Jon SmirlJun 16, 2006
  2. Linus TorvaldsJun 16, 2006
  3. Jon SmirlJun 16, 2006
  4. Linus TorvaldsJun 16, 2006
  5. Jon SmirlJun 16, 2006
  6. Jakub NarebskiJun 16, 2006
  7. Keith PackardJun 16, 2006
  8. Jon SmirlJun 16, 2006
  9. Keith PackardJun 16, 2006
  10. Nicolas PitreJun 16, 2006
  11. Linus TorvaldsJun 16, 2006

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.