From: Junio C Hamano Date: Mon, 02 Nov 2026 09:21:17 GMT Subject: Re: [PATCH v3] object-name: explain why ~N fails in a shallow clone Message-ID: In-Reply-To: "Harald Nordgren via GitGitGadget" writes: > From: Harald Nordgren > > Asking for a commit's ancestor with ~N in a shallow clone that > does not have N commits of history locally fails with a bare "is not > a commit" error, with no indication that the repository being shallow > is the reason, or what to do about it. > ... > Changes in v3: > > * Drop the git log -/--since extension entirely, per feedback that > last commit shown is an unreliable signal for a shallow boundary. > * Fix a bug for chained ^^^ where it would print the hint twice. We unfortunately haven't seen many folks interested in this change. Is anybody interested in reviewing the patch to give it a push? Unless we see some volunteers to give it a review in a few weeks, I will discard the topic out of my tree, as 'seen' has been crowded with topics that have been collecting dust without getting many reviews.