git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
ASAskar 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

Previous: Bagas SanjayaNext: Junio C Hamano
Message 3 of 4 in “git: list of my complaints about future graft removal”
  1. Askar SafinAug 19, 2025
  2. Bagas SanjayaAug 20, 2025
  3. Askar SafinAug 25, 2025
  4. Junio C HamanoAug 25, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.