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

Re: Fetching a lot of repos

From
SMStefan Moch <stefanmoch@mail.de>
Date
Jun 8, 2020, 17:14 UTC
Message-ID
<3540db7b-7175-18f8-fc5d-2b27c9298d14@mail.de>
In-Reply-To
<20200607210344.GK6569@camp.crustytoothpaste.net>
* brian m. carlson wrote:
Show 5 quoted lines
> In general, I wouldn't recommend fetching in parallel, but if you want
> to do it anyway, I'd suggest setting `receive.unpackLimit` to 1.  That
> will result in you keeping the packs you've fetched instead of exploding
> them into loose objects, which will help this case.  It may not help
> enough to solve the problem, though.

For fetch it should be `fetch.unpackLimit` (or `transfer.unpackLimit`), as `receive.unpackLimit` configures this limit for receive-pack.

Previous: brian m. carlson
Message 5 of 5 in “Fetching a lot of repos”
  1. Soni "They/Them" L.Jun 7, 2020
  2. brian m. carlsonJun 7, 2020
  3. Soni "They/Them" L.Jun 8, 2020
  4. brian m. carlsonJun 8, 2020
  5. Stefan MochJun 8, 2020

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.