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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 25, 2025, 23:36 UTC
Message-ID
<xmqq1poznfch.fsf@gitster.g>
In-Reply-To
<aKXXkvAOhStlS2_m@archie.me>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
Show 6 quoted lines
> On Tue, Aug 19, 2025 at 05:57:08PM +0400, Askar Safin wrote:
>> * As well as I understand, "git clone --depth=1" rely on grafts, too.
>> I hope "git clone --depth=1" will continue to work.
>
> So shallow clones should use git-replace(1) under the hood (both on initial
> clone, deepening with --shallow-since and --unshallow), right?

An unfortunate historical glitch is that shallow uses neither the grafts (which is being removed) nor replace but its own mechanism. It internally borrows the same "graft" code paths but the data is stored outside the normal grafts mechanism, if I understand correctly.

Previous: Askar Safin
Message 4 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.