From: Seyi Kuforiji <kuforiji98@gmail.com>
To: git@vger.kernel.org
Cc: ps@pks.im, Seyi Kuforiji <kuforiji98@gmail.com>
Subject: [PATCH v2 0/5] oidmap: migrate cleanup to oidmap_clear_with_free()
Date: Mon, 2 Mar 2026 21:00:12 +0100 [thread overview]
Message-ID: <20260302200018.75731-1-kuforiji98@gmail.com> (raw)
In-Reply-To: <20260227234213.17633-1-kuforiji98@gmail.com>
Hi,
This series replaces oidmap_clear(map, 1) with
oidmap_clear_with_free() and introduces explicit free callbacks
at the remaining call sites.
The old boolean-based API implicitly assumed plain free(),
which obscures ownership semantics and does not work well
when oidmap_entry is embedded inside larger structures.
The callback-based API makes cleanup explicit and type-safe,
and avoids relying on hidden assumptions about allocation.
This is used in subsequent commits to adequately cleanup all
usage site.
Changes in v2:
- fix missing .path cleanup
- modified commit message to be more accurate
Thanks
Seyi
Seyi Kufoiji (5):
oidmap: make entry cleanup explicit in oidmap_clear
builtin/rev-list: migrate missing_objects cleanup to
oidmap_clear_with_free()
list-objects-filter: use oidmap_clear_with_free() for cleanup
odb: use oidmap_clear_with_free() to release replace_map entries
sequencer: use oidmap_clear_with_free() for string_entry cleanup
builtin/rev-list.c | 15 ++++++++++++---
list-objects-filter.c | 9 ++++++++-
odb.c | 11 ++++++++++-
oidmap.c | 23 ++++++++++++++++++++---
oidmap.h | 15 +++++++++++++++
sequencer.c | 10 ++++++++--
t/unit-tests/u-oidmap.c | 41 +++++++++++++++++++++++++++++++++++++++++
7 files changed, 114 insertions(+), 10 deletions(-)
Range-diff against v1:
1: a0ab068630 < -: ---------- sparse-checkout: use string_list_sort_u
2: b2c0ee2593 < -: ---------- The 7th batch
3: 6af69c2c49 = 1: 1d544ef7d2 oidmap: make entry cleanup explicit in oidmap_clear
4: 452f5d8edb ! 2: f2c3a699bd builtin/rev-list: migrate missing_objects cleanup to oidmap_clear_with_free()
@@ Metadata
Author: Seyi Kufoiji <kuforiji98@gmail.com>
## Commit message ##
- builtin/rev-list: migrate missing_objects cleanup to oidmap_clear_with_free()
+ builtin/rev-list: migrate missing_objects cleanup to
+ oidmap_clear_with_free()
As part of the conversion away from oidmap_clear(), switch the
missing_objects map to use oidmap_clear_with_free().
@@ Commit message
Introduce a dedicated free callback and pass it to
oidmap_clear_with_free(), consolidating entry teardown into a
- single place and making cleanup semantics explicit. This improves
- clarity and maintainability.
+ single place and making cleanup semantics explicit.
Signed-off-by: Seyi Kuforiji <kuforiji98@gmail.com>
@@ builtin/rev-list.c: static int arg_print_omitted; /* print objects omitted by fi
+{
+ struct missing_objects_map_entry *entry =
+ container_of(e, struct missing_objects_map_entry, entry);
++
++ free(entry->path);
+ free(entry);
+}
+
5: cbfcc4e9cc = 3: a4e426bcca list-objects-filter: use oidmap_clear_with_free() for cleanup
6: bfbdb51d84 = 4: 4116e5491d odb: use oidmap_clear_with_free() to release replace_map entries
7: 4fc6e71f4c = 5: ad1f776a19 sequencer: use oidmap_clear_with_free() for string_entry cleanup
--
2.43.0
next prev parent reply other threads:[~2026-03-02 20:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 23:42 [PATCH 0/5] oidmap: migrate cleanup to oidmap_clear_with_free() Seyi Kuforiji
2026-02-27 23:42 ` [PATCH 1/5] oidmap: make entry cleanup explicit in oidmap_clear Seyi Kuforiji
2026-02-27 23:42 ` [PATCH 2/5] builtin/rev-list: migrate missing_objects cleanup to oidmap_clear_with_free() Seyi Kuforiji
2026-02-28 0:09 ` Junio C Hamano
2026-02-27 23:42 ` [PATCH 3/5] list-objects-filter: use oidmap_clear_with_free() for cleanup Seyi Kuforiji
2026-02-27 23:42 ` [PATCH 4/5] odb: use oidmap_clear_with_free() to release replace_map entries Seyi Kuforiji
2026-02-27 23:42 ` [PATCH 5/5] sequencer: use oidmap_clear_with_free() for string_entry cleanup Seyi Kuforiji
2026-03-02 20:00 ` Seyi Kuforiji [this message]
2026-03-02 20:00 ` [PATCH v2 1/5] oidmap: make entry cleanup explicit in oidmap_clear Seyi Kuforiji
2026-03-02 22:23 ` Junio C Hamano
2026-03-02 20:00 ` [PATCH v2 2/5] builtin/rev-list: migrate missing_objects cleanup to oidmap_clear_with_free() Seyi Kuforiji
2026-03-02 22:26 ` Junio C Hamano
2026-03-04 6:57 ` Patrick Steinhardt
2026-03-02 20:00 ` [PATCH v2 3/5] list-objects-filter: use oidmap_clear_with_free() for cleanup Seyi Kuforiji
2026-03-02 22:30 ` Junio C Hamano
2026-03-04 6:57 ` Patrick Steinhardt
2026-03-04 15:31 ` Junio C Hamano
2026-03-04 19:29 ` Seyi Kuforiji
2026-03-04 20:30 ` Junio C Hamano
2026-03-04 21:43 ` Junio C Hamano
2026-03-02 20:00 ` [PATCH v2 4/5] odb: use oidmap_clear_with_free() to release replace_map entries Seyi Kuforiji
2026-03-02 22:35 ` Junio C Hamano
2026-03-02 20:00 ` [PATCH v2 5/5] sequencer: use oidmap_clear_with_free() for string_entry cleanup Seyi Kuforiji
2026-03-02 22:38 ` Junio C Hamano
2026-03-04 6:57 ` Patrick Steinhardt
2026-03-05 10:05 ` [PATCH v3 0/2] oidmap: migrate cleanup to oidmap_clear_with_free() Seyi Kuforiji
2026-03-05 10:05 ` [PATCH v3 1/2] oidmap: make entry cleanup explicit in oidmap_clear Seyi Kuforiji
2026-03-05 10:05 ` [PATCH v3 2/2] builtin/rev-list: migrate missing_objects cleanup to oidmap_clear_with_free() Seyi Kuforiji
2026-03-05 14:27 ` [PATCH v3 0/2] oidmap: migrate " Patrick Steinhardt
2026-03-05 19:17 ` 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=20260302200018.75731-1-kuforiji98@gmail.com \
--to=kuforiji98@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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