diff options
author | Jeff King <peff@peff.net> | 2020-05-04 17:12:27 -0600 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-05-04 21:57:58 -0700 |
commit | 5bf7f1eaa51b3f35161e1c9e4d8bc843330dea3c (patch) | |
tree | 4947c967130e1c5d322a2fb305fd684c1bd63ebb /t/t3411-rebase-preserve-around-merges.sh | |
parent | The sixth batch (diff) | |
download | tgif-5bf7f1eaa51b3f35161e1c9e4d8bc843330dea3c.tar.xz |
list-objects-filter: treat NULL filter_options as "disabled"
In most callers, we have an actual list_objects_filter_options struct,
and if no filtering is desired its "choice" element will be
LOFC_DISABLED. However, some code may have only a pointer to such a
struct which may be NULL (because _their_ callers didn't care about
filtering, either). Rather than forcing them to handle this explicitly
like:
if (filter_options)
traverse_commit_list_filtered(filter_options, revs,
show_commit, show_object,
show_data, NULL);
else
traverse_commit_list(revs, show_commit, show_object,
show_data);
let's just treat a NULL filter_options the same as LOFC_DISABLED. We
only need a small change, since that option struct is converted into a
real filter only in the "init" function.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3411-rebase-preserve-around-merges.sh')
0 files changed, 0 insertions, 0 deletions