From: Junio C Hamano <gitster@pobox.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Askar Safin <safinaskar@zohomail.com>, git <git@vger.kernel.org>,
helpdesk <helpdesk@kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: git: list of my complaints about future graft removal
Date: Mon, 25 Aug 2025 16:36:46 -0700 [thread overview]
Message-ID: <xmqq1poznfch.fsf@gitster.g> (raw)
In-Reply-To: <aKXXkvAOhStlS2_m@archie.me> (Bagas Sanjaya's message of "Wed, 20 Aug 2025 21:11:30 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> 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.
prev parent reply other threads:[~2025-08-25 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 13:57 git: list of my complaints about future graft removal Askar Safin
2025-08-20 14:11 ` Bagas Sanjaya
2025-08-25 13:39 ` Askar Safin
2025-08-25 23:36 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1poznfch.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=helpdesk@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-doc@vger.kernel.org \
--cc=safinaskar@zohomail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).