All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Samo Pogačnik" <samo_pogacnik@t-2.net>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
	Taylor Blau <me@ttaylorr.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH v2] shallow: set borders which are all reachable after clone shallow since
Date: Fri, 06 Feb 2026 21:19:13 -0800	[thread overview]
Message-ID: <xmqqy0l5b06m.fsf@gitster.g> (raw)
In-Reply-To: <a60fc6aed8ab7345219118f933ac0eb61140334f.camel@t-2.net> ("Samo Pogačnik"'s message of "Sat, 07 Feb 2026 06:06:01 +0100")

Samo Pogačnik <samo_pogacnik@t-2.net> writes:

> 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.

  reply	other threads:[~2026-02-07  5:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22 10:38 [PATCH] Fixed --shallow-since generating descendant borders Samo Pogačnik via GitGitGadget
2025-11-22 17:36 ` Junio C Hamano
2025-11-23 19:35 ` [PATCH v2] shallow: set borders which are all reachable after clone shallow since Samo Pogačnik via GitGitGadget
2025-11-25  0:43   ` Junio C Hamano
2026-01-20 20:59     ` Junio C Hamano
2026-01-28  4:23       ` Samo Pogačnik
2026-02-07  5:06         ` Samo Pogačnik
2026-02-07  5:19           ` Junio C Hamano [this message]
2026-03-07  7:13             ` Samo Pogačnik
2026-01-31 16:28   ` [PATCH v3] shallow: ensure all boundary commits are reachable with --shallow-since Samo Pogačnik via GitGitGadget

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=xmqqy0l5b06m.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=ps@pks.im \
    --cc=samo_pogacnik@t-2.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.