From: "Samo Pogačnik" <samo_pogacnik@t-2•net>
To: Patrick Steinhardt <ps@pks•im>, Taylor Blau <me@ttaylorr•com>,
Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [PATCH v2] shallow: set borders which are all reachable after clone shallow since
Date: Sat, 07 Mar 2026 08:13:40 +0100 [thread overview]
Message-ID: <418dfce27b2812a696dee791e81a0049400e50f4.camel@t-2.net> (raw)
In-Reply-To: <xmqqy0l5b06m.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Fri, 2026-02-06 at 21:19 -0800, Junio C Hamano wrote:
> 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/
>
Could you please check this correction.
Thanks, Samo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-07 7:21 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
2026-03-07 7:13 ` Samo Pogačnik [this message]
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=418dfce27b2812a696dee791e81a0049400e50f4.camel@t-2.net \
--to=samo_pogacnik@t-2$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=ps@pks$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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