Re: git: list of my complaints about future graft removal
- From
- Askar Safin <safinaskar@zohomail.com>
- Date
- Aug 25, 2025, 13:39 UTC
- Message-ID
- <198e1742f3e.aebc766525693.2818180197972770618@zohomail.com>
- In-Reply-To
- <aKXXkvAOhStlS2_m@archie.me>
---- On Wed, 20 Aug 2025 18:11:30 +0400 Bagas Sanjaya <bagasdotme@gmail.com> wrote --- > So shallow clones should use git-replace(1) under the hood (both on initial > clone, deepening with --shallow-since and --unshallow), right?
You are asking me? I'm not git developer.
What you mean? How git works currently or how it should work in 3.0?
I don't know how it works currently.
And I don't know how it will work in the future.
I just want "git clone --depth=1" to continue to work. I. e. git developers should somehow take measures to make sure "git clone --depth=1" will continue to work even if grafts will be removed.
Currently "git clone --depth=1" seems to be implemented using grafts, i. e. I see word "grafted" in "git log" output if I use "git clone --depth=1" (I just tested this on git 2.47.2)
-- Askar Safin https://types.pl/@safinaskar