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

Re: Something is broken in repack. Why not with fork and pipes?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 12, 2007, 19:41 UTC
Message-ID
<Pine.LNX.4.64.0712121939210.27959@racer.site>
In-Reply-To
<998d0e4a0712121047m3cb09f37qc3157b96e5d171e7@mail.gmail.com>
Hi,
On Wed, 12 Dec 2007, J.C. Pizarro wrote:
> It's good idea if it's for 24/365.25 that it does
>  autorepack-compute-again-again-again-those-unexplored-deltas of
>  git repositories in realtime. :D
This sentence does not parse.
> Some body can do "git clone" that it could give smaller that one hour ago :D
Neither does this.
> To Linus, Why don't you forget the threaded implementation of your 
> repo-pack?

Please do a little research before you ask such questions: it is neither Linus who did it, nor is it better to use processes than threads.

Besides, your proposal has nothing to do with the issue of this thread (memory consumption).

Ciao, Dscho

Previous: J.C. Pizarro
Message 2 of 2 in “Re: Something is broken in repack. Why not with fork and pipes?”
  1. J.C. PizarroDec 12, 2007
  2. Johannes SchindelinDec 12, 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.