Re: git: list of my complaints about future graft removal

Askar Safin <[email protected]> Mon, 25 Aug 2025 17:39:04 +0400
Newsgroups gmane.linux.documentation,gmane.comp.version-control.git,gmane.linux.kernel.kernelnewbies,gmane.linux.kernel.janitors
Message-ID <[email protected]>
 ---- On Wed, 20 Aug 2025 18:11:30 +0400  Bagas Sanjaya <[email protected]> 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