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

Re: [PATCH v2] shallow: set borders which are all reachable after clone shallow since

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 7, 2026, 05:19 UTC
Message-ID
<xmqqy0l5b06m.fsf@gitster.g>
In-Reply-To
<a60fc6aed8ab7345219118f933ac0eb61140334f.camel@t-2.net>
Samo Pogačnik <samo_pogacnik@t-2.net> writes:
Show 18 quoted lines
> On Wed, 2026-01-28 at 05:23 +0100, Samo Pogačnik wrote:
>> On Tue, 2026-01-20 at 12:59 -0800, Junio C Hamano wrote:
>> ...
>> > After this exchange, the topic has been dormant for almost full two
>> > months.  As I do not deal with shallow clones myself, even though I
>> > understand that some folks rely on it working, I'd really prefer to
>> > see somebody who are familiar with the underlying logic to review
>> > this patch if we were to move forward with it.
>> > 
>> 
>> I’m currently rewriting the patch and the commit message trying to
>> address the boundary/border dilemma. I hope to be able to send a new
>> version by the end of this week.
>
> I posted a new version of patch '[PATCH v3] shallow: ensure all boundary commits
> are reachable with --shallow-since' on 31st of January. I hope you've seen it.
>
> thanks, Samo

For those of you on the original CC: list taken from v2 review thread, who may be more qualified to review this topic than I am, the v3 is found at:

  https://lore.kernel.org/git/pull.2107.v3.git.git.1769876930544.gitgitgadget@gmail.com/
Thanks.
Previous: Samo PogačnikNext: Samo Pogačnik
Message 8 of 10 in “Fixed --shallow-since generating descendant borders”
  1. Fixed --shallow-since generating descendant bordersSamo Pogačnik via GitGitGadget, Nov 22, 2025
  2. Junio C HamanoNov 22, 2025
  3. shallow: set borders which are all reachable after clone shallow sinceSamo Pogačnik via GitGitGadget, Nov 23, 2025
  4. Junio C HamanoNov 25, 2025
  5. Junio C HamanoJan 20, 2026
  6. Samo PogačnikJan 28, 2026
  7. Samo PogačnikFeb 7, 2026
  8. Junio C HamanoFeb 7, 2026
  9. Samo PogačnikMar 7, 2026
  10. shallow: ensure all boundary commits are reachable with --shallow-sinceSamo Pogačnik via GitGitGadget, Jan 31, 2026

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.