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

[PATCH 0/3] the return of the strbuf

From
Pierre Habouzit <madcoder@debian.org>
Date
Sep 17, 2007, 12:52 UTC
Message-ID
<20070917125211.GA18176@artemis.corp>
  While getting rid of ->eof in strbuf (as it was somehow tasteless). It
made me aware of the fact that fast-import.c was using a custom buffer
implementation (I think that was the fourth if not the fifth). So here
is the series that eradicates it.
  Trying to understand fast-import.c code, I happened to remark that it
was possible to avoid many reallocations, just by reusing old buffers
rather than dropping them (this was not possible in a readable way
before, but it is now, and uses the same mechanisms that was garbage
collecting buffers, to swap them instead).
  I've not enough stuff to do real-life tests of the old fast-import and
the new one, but I wouldn't be surprised that it gives a quite nice
speed improvements for tools that use long fast-import batches. If not,
well, the code is shorter and more readable, hence it's still a gain.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Next: Pierre Habouzit
Message 1 of 11 in “the return of the strbuf”
  1. 0/3 the return of the strbufPierre Habouzit, Sep 17, 2007
  2. 1/3 Drop strbuf's 'eof' marker, and make read_line a first class citizen.Pierre Habouzit, Sep 17, 2007
  3. 2/3 fast-import was using dbuf's, replace them with strbuf's.Pierre Habouzit, Sep 17, 2007
  4. 3/3 fast-import optimization:Pierre Habouzit, Sep 17, 2007
  5. Pierre HabouzitSep 17, 2007
  6. Shawn O. PearceSep 18, 2007
  7. Johannes SchindelinSep 20, 2007
  8. Shawn O. PearceSep 20, 2007
  9. Junio C HamanoSep 20, 2007
  10. Johannes SchindelinSep 20, 2007
  11. Junio C HamanoSep 18, 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.