From: Patrick Steinhardt <ps@pks•im>
To: Bagas Sanjaya <bagasdotme@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>,
Junio C Hamano <gitster@pobox•com>, Jeff King <peff@peff•net>,
"brian m. carlson" <sandals@crustytoothpaste•net>,
Taylor Blau <me@ttaylorr•com>,
Askar Safin <safinaskar@zohomail•com>
Subject: Re: Shallow clone support in v3.0 and beyond?
Date: Wed, 10 Sep 2025 13:08:15 +0200 [thread overview]
Message-ID: <aMFcH2nfKO-DZcwm@pks.im> (raw)
In-Reply-To: <aKzy6naLtdeq7Tgn@archie.me>
Hi,
On Tue, Aug 26, 2025 at 06:34:02AM +0700, Bagas Sanjaya wrote:
> Hi,
>
> Askar Safin <safinaskar@zohomail•com> posted on the ML about his complaints
> regarding grafts removal in v3.0+ (see [1] for the full thread). He also
> briefly mentioned future of shallow clones (aka git clone --depth=1).
>
> The question is: If grafts support is removed, then how can shallow clones
> be implemented in terms of git-replace(1)? What about its implementation
> details? How about unshallowing (git fetch --unshallow)?
>
> Thanks.
>
> [1]: https://lore.kernel.org/git/198c29e9058.119e3a5c065010.5888624019176274871@zohomail.com/T/#t
I think the BreakingChanges document could use a revamp in that regard.
The mechanism used to implement shallow clones is of course _not_ going
away, and the internal mechanism to facilitate this will go away.
So the intention really only to remove ".git/info/grafts" as a
user-visible mechanism. Users should exclusively use git-replace(1).
Patrick
next prev parent reply other threads:[~2025-09-10 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 23:34 Shallow clone support in v3.0 and beyond? Bagas Sanjaya
2025-09-10 11:08 ` Patrick Steinhardt [this message]
2025-09-10 11:13 ` Bagas Sanjaya
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=aMFcH2nfKO-DZcwm@pks.im \
--to=ps@pks$(echo .)im \
--cc=bagasdotme@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=safinaskar@zohomail$(echo .)com \
--cc=sandals@crustytoothpaste$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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