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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 04, 2025 at 12:33:08PM +0300, Дилян Палаузов wrote:
> 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





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux