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

Re: Suggetsions for collaboration workflows in large repos

From
Matthew Hughes <matthewhughes934@gmail.com>
Date
Jun 2, 2026, 18:35 UTC
Message-ID
<ah8W5BL714h9r3_c@desktop>
In-Reply-To
<82F556A1-A5C6-414E-8EFB-13F83FA30E44@gmail.com>
On Fri, May 29, 2026 at 01:56:02PM -0400, Ben Knoble wrote:
> My current advice is to enable git-maintenance on such a repo, where
> prefetches and commit graphs and so on will give you a nice perf boost. Then
> I keep the default fetch all heads config and don’t mind the noise too much.

Thanks, I do have maintenance activated (I believe `scalar` handled that for me) and that does noticeable speed up some operations, and I have find the performance in general for almost all operations to be much better than I expected (having not worked in such a large repo before). My only real issue is in fetching, since I really don't want to waste the time pulling down all the other branches in the repo that I almost certainly will never need locally.

Previous: Ben KnobleNext: Matthew Hughes
Message 3 of 5 in “Suggetsions for collaboration workflows in large repos”
  1. Matthew HughesMay 29, 2026
  2. Ben KnobleMay 29, 2026
  3. Matthew HughesJun 2, 2026
  4. Matthew HughesMay 29, 2026
  5. Toon ClaesJun 3, 2026

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.