diff options
author | Jonathan Tan <jonathantanmy@google.com> | 2018-06-07 12:04:13 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-06-21 11:17:39 -0700 |
commit | 3ae5fa0768f7f9781b40b1d40cb2f9f4c753bad4 (patch) | |
tree | 3dbff4abb2a2a97d3b18307599e91d72969818ea /t/t4013/diff.diff-tree_--cc_--patch-with-stat_--summary_side | |
parent | Git 2.18 (diff) | |
download | tgif-3ae5fa0768f7f9781b40b1d40cb2f9f4c753bad4.tar.xz |
pack-bitmap: remove bitmap_git global variable
Remove the bitmap_git global variable. Instead, generate on demand an
instance of struct bitmap_index for code that needs to access it.
This allows us significant control over the lifetime of instances of
struct bitmap_index. In particular, packs can now be closed without
worrying if an unnecessarily long-lived "pack" field in struct
bitmap_index still points to it.
The bitmap API is also clearer in that we need to first obtain a struct
bitmap_index, then we use it.
This patch raises two potential issues: (1) memory for the struct
bitmap_index is allocated without being freed, and (2)
prepare_bitmap_git() and prepare_bitmap_walk() can reuse a previously
loaded bitmap. For (1), this will be dealt with in a subsequent patch in
this patch set that also deals with freeing the contents of the struct
bitmap_index (which were not freed previously, because they have global
scope). For (2), current bitmap users only load the bitmap once at most
(note that pack-objects can use bitmaps or write bitmaps, but not both
at the same time), so support for reuse has no effect - and future users
can pass around the struct bitmap_index * obtained if they need to do 2
or more things with the same bitmap.
Helped-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Jonathan Tan <jonathantanmy@google.com>
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.diff-tree_--cc_--patch-with-stat_--summary_side')
0 files changed, 0 insertions, 0 deletions