From: Patrick Steinhardt <ps@pks.im>
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: Fri, 5 Sep 2025 16:30:14 +0200 [thread overview]
Message-ID: <aLrz9j8pUmHawNcz@pks.im> (raw)
In-Reply-To: <a1f72b71-2068-4526-920b-bab82137a509@gmail.com>
On Fri, Sep 05, 2025 at 09:40:49AM -0400, Derrick Stolee wrote:
> On 9/5/2025 8:23 AM, Patrick Steinhardt wrote:
> > On Thu, Sep 04, 2025 at 08:19:59AM -0400, Derrick Stolee wrote:
>
> > So in general, the recommendation I typically give is to not use
> > treeless clones at all.
>
> Rather, I'd say that treeless clones are useful if you want the
> speed of a shallow clone with some need to analyze commit history
> (with no path history) for an ephemeral scenario like a CI build.
>
> Treeless clones are not a good approach for doing ongoing work as
> a human. They are a tool for a very narrow case, so don't use them
> unless you understand how to avoid their pitfalls.
Ah, yes. I should've quantified my statement a bit more carefully.
Thanks for adding in this angle.
Patrick
next prev parent reply other threads:[~2025-09-05 14:30 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
2025-09-05 12:23 ` Patrick Steinhardt
2025-09-05 13:40 ` Derrick Stolee
2025-09-05 14:30 ` Patrick Steinhardt [this message]
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=aLrz9j8pUmHawNcz@pks.im \
--to=ps@pks.im \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.