git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
	"Дилян Палаузов" <dilyan.palauzov@aegee.org>,
	git <git@vger.kernel.org>
Subject: Re: Doing blobless clone by default; switching between blobless, treeless and full clones by a command
Date: Thu, 04 Sep 2025 09:47:57 -0700	[thread overview]
Message-ID: <xmqqikhy9nb6.fsf@gitster.g> (raw)
In-Reply-To: <7713256d-e258-4356-b303-128fdb417972@gmail.com> (Derrick Stolee's message of "Thu, 4 Sep 2025 08:19:59 -0400")

Derrick Stolee <stolee@gmail.com> writes:

> But there was always the possibility that the feedback from having
> 'scalar clone' available could lead to a future builtin of the form
> 'git big-clone' that adds similar optimizations for large repos. (My
> opinion is that 'scalar clone' _is_ this 'git big-clone' but maybe it
> is not discoverable enough.)

A separate command like "bit-clone" would not be discoverable
enough, either.  When a new feature matures in the playground, it
would be a welcome change for "git clone" to borrow it as a new
option, or even better yet, automatically enable it depending on the
size of the thing, with end-user consent.

Thanks.

  reply	other threads:[~2025-09-04 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04  9:33 Doing blobless clone by default; switching between blobless, treeless and full clones by a command Дилян Палаузов
2025-09-04  9:41 ` Kristoffer Haugsbakk
2025-09-04 12:19   ` Derrick Stolee
2025-09-04 16:47     ` Junio C Hamano [this message]
2025-09-05 12:23     ` Patrick Steinhardt
2025-09-05 13:40       ` Derrick Stolee
2025-09-05 14:30         ` Patrick Steinhardt
2025-09-05 14:49 ` Konstantin Ryabitsev
2025-09-07 19:42 ` Ben Knoble

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqikhy9nb6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=dilyan.palauzov@aegee.org \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=stolee@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).