From: "Samo Pogačnik via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Patrick Steinhardt" <ps@pks.im>,
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
"Samo Pogačnik" <samo_pogacnik@t-2.net>
Subject: [PATCH v5 0/2] shallow: handling fetch relative-deepen
Date: Sun, 15 Feb 2026 20:11:54 +0000 [thread overview]
Message-ID: <pull.2121.v5.git.git.1771186316.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2121.v4.git.git.1768602661.gitgitgadget@gmail.com>
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.
On the other hand, it seems that equivalent absolute depth driven fetches
result in all the correct shallows. That led to this proposal, which unifies
absolute and relative deepening in a way that the same get_shallow_commits()
call is used in both cases. The difference is only that depth is adapted for
relative deepening by measuring equivalent depth of current local shallow
commits in the current remote repo. Thus a new function get_shallows_depth()
has been added and the function get_reachable_list() became redundant /
removed.
The get_shallows_depth() function also shares the logic of the
get_shallow_commits() function, but it focuses on counting depth of each
existing shallow commit. The minimum result is stored as
'data->deepen_relative', which is set not to be zero for relative deepening
anyway. That way we can allways summ 'data->deepen_relative' and 'depth'
values, because 'data->deepen_relative' is always 0 in absolute deepening.
Samo Pogačnik (2):
shallow: free local object_array allocations
shallow: handling fetch relative-deepen
shallow.c | 73 ++++++++++++++++++++++++++++++++++++-------
shallow.h | 2 ++
t/t5500-fetch-pack.sh | 23 ++++++++++++++
upload-pack.c | 72 ++----------------------------------------
4 files changed, 88 insertions(+), 82 deletions(-)
base-commit: f0ef5b6d9bcc258e4cbef93839d1b7465d5212b9
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2121%2Fspog%2Ffix-fetch-deepen-v5
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2121/spog/fix-fetch-deepen-v5
Pull-Request: https://github.com/git/git/pull/2121
Range-diff vs v4:
1: f8a8d077cd = 1: f8a8d077cd shallow: free local object_array allocations
2: e9b20ae06f ! 2: 8d48ba9cd1 shallow: handling fetch relative-deepen
@@ Commit message
Signed-off-by: Samo Pogačnik <samo_pogacnik@t-2.net>
+ Fixing v4
+
+ Fixing v4 again
+
## shallow.c ##
@@ shallow.c: static void free_depth_in_slab(int **ptr)
{
@@ shallow.c: static void free_depth_in_slab(int **ptr)
}
-struct commit_list *get_shallow_commits(struct object_array *heads, int depth,
- int shallow_flag, int not_shallow_flag)
-+struct commit_list *get_shallow_commits(struct object_array *heads,
-+ struct object_array *shallows, int *deepen_relative,
-+ int depth, int shallow_flag, int not_shallow_flag)
++/*
++ * This is a common internal function that can either return a list of
++ * shallow commits or calculate the current maximum depth of a shallow
++ * repository, depending on the input parameters.
++ *
++ * Depth calculation is triggered by passing the `shallows` parameter.
++ * In this case, the computed depth is stored in `max_cur_depth` (if it is
++ * provided), and the function returns NULL.
++ *
++ * Otherwise, `max_cur_depth` remains unchanged and the function returns
++ * a list of shallow commits.
++ */
++static struct commit_list *get_shallows_or_depth(struct object_array *heads,
++ struct object_array *shallows, int *max_cur_depth,
++ int depth, int shallow_flag, int not_shallow_flag)
{
-- size_t i = 0;
+ size_t i = 0;
- int cur_depth = 0;
-+ size_t i = 0, j;
+ int cur_depth = 0, cur_depth_shallow = 0;
struct commit_list *result = NULL;
struct object_array stack = OBJECT_ARRAY_INIT;
@@ shallow.c: struct commit_list *get_shallow_commits(struct object_array *heads, i
- commit = NULL;
- continue;
+ if (shallows) {
-+ for (j = 0; j < shallows->nr; j++)
++ for (size_t j = 0; j < shallows->nr; j++)
+ if (oideq(&commit->object.oid, &shallows->objects[j].item->oid))
-+ if ((!cur_depth_shallow) || (cur_depth < cur_depth_shallow))
++ if (!cur_depth_shallow || cur_depth < cur_depth_shallow)
+ cur_depth_shallow = cur_depth;
+
+ if ((is_repository_shallow(the_repository) && !commit->parents &&
@@ shallow.c: struct commit_list *get_shallow_commits(struct object_array *heads, i
int **depth_slot = commit_depth_at(&depths, p->item);
if (!*depth_slot) {
@@ shallow.c: struct commit_list *get_shallow_commits(struct object_array *heads, int depth,
- }
deep_clear_commit_depth(&depths, free_depth_in_slab);
object_array_clear(&stack);
--
-+ if (shallows && deepen_relative)
-+ *deepen_relative = cur_depth_shallow;
+
++ if (shallows && max_cur_depth)
++ *max_cur_depth = cur_depth_shallow;
return result;
}
++int get_shallows_depth(struct object_array *heads, struct object_array *shallows)
++{
++ int max_cur_depth = 0;
++ get_shallows_or_depth(heads, shallows, &max_cur_depth, 0, 0, 0);
++ return max_cur_depth;
++
++}
++
++struct commit_list *get_shallow_commits(struct object_array *heads,
++ struct object_array *shallows, int deepen_relative,
++ int depth, int shallow_flag, int not_shallow_flag)
++{
++ if (shallows && deepen_relative) {
++ depth += get_shallows_depth(heads, shallows);
++ }
++ return get_shallows_or_depth(heads, NULL, NULL,
++ depth, shallow_flag, not_shallow_flag);
++}
++
+ static void show_commit(struct commit *commit, void *data)
+ {
+ commit_list_insert(commit, data);
## shallow.h ##
@@ shallow.h: int commit_shallow_file(struct repository *r, struct shallow_lock *lk);
+ /* rollback $GIT_DIR/shallow and reset stat-validity checks */
void rollback_shallow_file(struct repository *r, struct shallow_lock *lk);
++int get_shallows_depth(struct object_array *heads, struct object_array *shallows);
struct commit_list *get_shallow_commits(struct object_array *heads,
-+ struct object_array *shallows, int *deepen_relative,
++ struct object_array *shallows, int deepen_relative,
int depth, int shallow_flag, int not_shallow_flag);
struct commit_list *get_shallow_commits_by_rev_list(struct strvec *argv,
int shallow_flag, int not_shallow_flag);
@@ upload-pack.c: error:
-static int get_reachable_list(struct upload_pack_data *data,
- struct object_array *reachable)
-+static void get_shallows_depth(struct upload_pack_data *data)
- {
+-{
- struct child_process cmd = CHILD_PROCESS_INIT;
- int i;
- struct object *o;
@@ upload-pack.c: error:
-out:
- child_process_clear(&cmd);
- return ret;
-+ get_shallow_commits(&data->want_obj, &data->shallows,
-+ &data->deepen_relative, 0,
-+ SHALLOW, NOT_SHALLOW);
- }
-
+-}
+-
static int has_unreachable(struct object_array *src, enum allow_uor allow_uor)
+ {
+ struct child_process cmd = CHILD_PROCESS_INIT;
@@ upload-pack.c: static void deepen(struct upload_pack_data *data, int depth)
struct object *object = data->shallows.objects[i].item;
object->flags |= NOT_SHALLOW;
@@ upload-pack.c: static void deepen(struct upload_pack_data *data, int depth)
struct commit_list *result;
- result = get_shallow_commits(&data->want_obj, depth,
-+ if (data->deepen_relative)
-+ get_shallows_depth(data);
-+
-+ result = get_shallow_commits(&data->want_obj, NULL, NULL,
-+ data->deepen_relative + depth,
++ result = get_shallow_commits(&data->want_obj, &data->shallows,
++ data->deepen_relative, depth,
SHALLOW, NOT_SHALLOW);
send_shallow(data, result);
free_commit_list(result);
--
gitgitgadget
next prev parent reply other threads:[~2026-02-15 20:12 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 ` Samo Pogačnik via GitGitGadget [this message]
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 ` [PATCH v5 0/2] " Junio C Hamano
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=pull.2121.v5.git.git.1771186316.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--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