[PATCH v4 09/16] midx: don't free midx_name early
- From
Taylor Blau <me@ttaylorr.com>
- Date
- Mar 30, 2021, 15:04 UTC
- Message-ID
- <33b8af97e7c6fb2d3016422d084eae7aca7cb70c.1617116623.git.me@ttaylorr.com>
- In-Reply-To
- <cover.1617116623.git.me@ttaylorr.com>
A subsequent patch will need to refer back to 'midx_name' later on in the function. In fact, this variable is already free()'d later on, so this makes the later free() no longer redundant.
Signed-off-by: Taylor Blau <me@ttaylorr.com> --- midx.c | 1 - 1 file changed, 1 deletion(-)
diff --git a/midx.c b/midx.c index 4a9d84352c..3edde2b68d 100644 --- a/midx.c +++ b/midx.c @@ -956,7 +956,6 @@ static int write_midx_internal(const char *object_dir, struct multi_pack_index * hold_lock_file_for_update(&lk, midx_name, LOCK_DIE_ON_ERROR); f = hashfd(get_lock_file_fd(&lk), get_lock_file_path(&lk)); - FREE_AND_NULL(midx_name); if (ctx.m) close_midx(ctx.m);
-- 2.30.0.667.g81c0cbc6fd