# Shallow clone support in v3.0 and beyond? 3 messages from 2025-08-25 to 2025-09-10. Participants: Bagas Sanjaya, Patrick Steinhardt. Thread: https://gitlist.dev/t/64032 ## Bagas Sanjaya, 2025-08-25 23:34 Subject: Shallow clone support in v3.0 and beyond? Message-ID: URL: https://gitlist.dev/e/aKzy6naLtdeq7Tgn%40archie.me ``` Hi, Askar Safin 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 -- An old man doll... just what I always wanted! - Clara ``` ## Patrick Steinhardt, 2025-09-10 11:08 Subject: Re: Shallow clone support in v3.0 and beyond? Message-ID: URL: https://gitlist.dev/e/aMFcH2nfKO-DZcwm%40pks.im In-Reply-To: ``` Hi, On Tue, Aug 26, 2025 at 06:34:02AM +0700, Bagas Sanjaya wrote: > Hi, > > Askar Safin 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 ``` ## Bagas Sanjaya, 2025-09-10 11:13 Subject: Re: Shallow clone support in v3.0 and beyond? Message-ID: URL: https://gitlist.dev/e/dca4e74e-26ae-401d-bac9-f8b6f13296ef%40gmail.com In-Reply-To: ``` On 9/10/25 18:08, Patrick Steinhardt wrote: > Hi, > > On Tue, Aug 26, 2025 at 06:34:02AM +0700, Bagas Sanjaya wrote: >> Hi, >> >> Askar Safin 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). OK, thanks! -- An old man doll... just what I always wanted! - Clara ```