Skip to content

Commit f1230fb

Browse files
rscharfegitster
authored andcommitted
revision: remove the unused flag leak_pending
Signed-off-by: Rene Scharfe <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent a9a03fa commit f1230fb

File tree

2 files changed

+1
-14
lines changed

2 files changed

+1
-14
lines changed

revision.c

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2850,8 +2850,7 @@ int prepare_revision_walk(struct rev_info *revs)
28502850
}
28512851
}
28522852
}
2853-
if (!revs->leak_pending)
2854-
object_array_clear(&old_pending);
2853+
object_array_clear(&old_pending);
28552854

28562855
/* Signal whether we need per-parent treesame decoration */
28572856
if (revs->simplify_merges ||

revision.h

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -150,18 +150,6 @@ struct rev_info {
150150
date_mode_explicit:1,
151151
preserve_subject:1;
152152
unsigned int disable_stdin:1;
153-
/*
154-
* Set `leak_pending` to prevent `prepare_revision_walk()` from clearing
155-
* the array of pending objects (`pending`). It will still forget about
156-
* the array and its entries, so they really are leaked. This can be
157-
* useful if the `struct object_array` `pending` is copied before
158-
* calling `prepare_revision_walk()`. By setting `leak_pending`, you
159-
* effectively claim ownership of the old array, so you should most
160-
* likely call `object_array_clear(&pending_copy)` once you are done.
161-
* Observe that this is about ownership of the array and its entries,
162-
* not the commits referenced by those entries.
163-
*/
164-
unsigned int leak_pending:1;
165153
/* --show-linear-break */
166154
unsigned int track_linear:1,
167155
track_first_time:1,

0 commit comments

Comments
 (0)