From: Junio C Hamano <gitster@pobox.com>
To: "Samo Pogačnik via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>,
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
"Samo Pogačnik" <samo_pogacnik@t-2.net>
Subject: Re: [PATCH v5 0/2] shallow: handling fetch relative-deepen
Date: Fri, 20 Feb 2026 14:34:45 -0800 [thread overview]
Message-ID: <xmqqseavujqy.fsf@gitster.g> (raw)
In-Reply-To: <pull.2121.v5.git.git.1771186316.gitgitgadget@gmail.com> ("Samo Pogačnik via GitGitGadget"'s message of "Sun, 15 Feb 2026 20:11:54 +0000")
"Samo Pogačnik via GitGitGadget" <gitgitgadget@gmail.com> writes:
> When a shallowed repository gets deepened beyond the beginning of a merged
> branch, we may endup with some shallows, that are behind the reachable ones.
> Added test 'fetching deepen beyond merged branch' exposes that behaviour.
We didn't see any response to the latest round, and the comments on
previous rounds seem to have been addressed. Is this ready to be
merged down to 'next' now?
Thanks.
prev parent reply other threads:[~2026-02-20 22:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 18:11 [PATCH 0/2] shallow: handling fetch relative-deepen Samo Pogačnik via GitGitGadget
2025-12-09 18:11 ` [PATCH 1/2] shallow: free local object_array allocations Samo Pogačnik via GitGitGadget
2026-01-06 7:44 ` Patrick Steinhardt
2026-01-09 16:21 ` Samo Pogačnik
2026-01-09 16:33 ` Patrick Steinhardt
2025-12-09 18:11 ` [PATCH 2/2] shallow: handling fetch relative-deepen Samo Pogačnik via GitGitGadget
2026-01-06 7:44 ` Patrick Steinhardt
2026-01-09 16:48 ` Samo Pogačnik
2026-01-09 22:23 ` [PATCH v2 0/2] " Samo Pogačnik via GitGitGadget
2026-01-09 22:23 ` [PATCH v2 1/2] shallow: free local object_array allocations Samo Pogačnik via GitGitGadget
2026-01-09 22:23 ` [PATCH v2 2/2] shallow: handling fetch relative-deepen Samo Pogačnik via GitGitGadget
2026-01-10 4:17 ` Junio C Hamano
2026-01-10 5:13 ` [PATCH v3 0/2] " Samo Pogačnik via GitGitGadget
2026-01-10 5:13 ` [PATCH v3 1/2] shallow: free local object_array allocations Samo Pogačnik via GitGitGadget
2026-01-10 5:13 ` [PATCH v3 2/2] shallow: handling fetch relative-deepen Samo Pogačnik via GitGitGadget
2026-01-15 15:50 ` Kristoffer Haugsbakk
2026-01-16 22:30 ` [PATCH v4 0/2] " Samo Pogačnik via GitGitGadget
2026-01-16 22:31 ` [PATCH v4 1/2] shallow: free local object_array allocations Samo Pogačnik via GitGitGadget
2026-01-16 22:31 ` [PATCH v4 2/2] shallow: handling fetch relative-deepen Samo Pogačnik via GitGitGadget
2026-02-11 13:38 ` Patrick Steinhardt
2026-02-13 20:48 ` Samo Pogačnik
2026-02-14 9:40 ` Samo Pogačnik
2026-02-15 11:19 ` Samo Pogačnik
2026-02-15 20:11 ` [PATCH v5 0/2] " Samo Pogačnik via GitGitGadget
2026-02-15 20:11 ` [PATCH v5 1/2] shallow: free local object_array allocations Samo Pogačnik via GitGitGadget
2026-02-15 20:11 ` [PATCH v5 2/2] shallow: handling fetch relative-deepen Samo Pogačnik via GitGitGadget
2026-02-20 22:34 ` 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=xmqqseavujqy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=kristofferhaugsbakk@fastmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox