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

Re: Doing blobless clone by default; switching between blobless, treeless and full clones by a command

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Sep 5, 2025, 14:49 UTC
Message-ID
<20250905-markhor-of-impossible-happiness-df5e58@lemur>
In-Reply-To
<79ed51fbd94ec2793ab0388b33963b366e48c590.camel@aegee.org>
On Thu, Sep 04, 2025 at 12:33:08PM +0300, Дилян Палаузов wrote:
Show 13 quoted lines
> Rationale:
> 
> The reason people execute  git clone  is hardly to issue immediately
> afterwards  git log  or  git annotate.  The reason for git clone is to (try
> changing something and then) build the software. (Provided that git manages
> source code.)  Doing by default a reduced data download with  git clone
> will sped up the initialization, it will save bytes in transit and reduce
> server load.  In fact I think that by default (without extra configuration)
> git clone  should do a reduced download (blobless) and git should download
> the other things, when asked to do so.  This default download preference
> should be ideally managed by an option in global gitconfig .  When looking
> at https://git-scm.com/docs/git-config for “filter” I do not recognize
> anything relevant.

As a counter-rationale, shallow clones generate a lot more load on the server side, because there are no packs available for this operation. Making this the default behaviour will likely result in slower clones for everyone and more unavailable servers due to high load.

-K
Previous: Patrick SteinhardtNext: Ben Knoble
Message 8 of 9 in “Doing blobless clone by default; switching between blobless, treeless and full clones by a command”
  1. Дилян ПалаузовSep 4, 2025
  2. Kristoffer HaugsbakkSep 4, 2025
  3. Derrick StoleeSep 4, 2025
  4. Junio C HamanoSep 4, 2025
  5. Patrick SteinhardtSep 5, 2025
  6. Derrick StoleeSep 5, 2025
  7. Patrick SteinhardtSep 5, 2025
  8. Konstantin RyabitsevSep 5, 2025
  9. Ben KnobleSep 7, 2025

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.