Re: [PATCH 0/3] git for-each-ref: is-base atom and base branches
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 1, 2024, 23:06 UTC
- Message-ID
- <xmqqmslvhmgm.fsf@gitster.g>
- In-Reply-To
- <pull.1768.git.1722550226.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 13 quoted lines
> Derrick Stolee (3): > commit-reach: add get_branch_base_for_tip > for-each-ref: add 'is-base' token > p1500: add is-base performance tests > > commit-reach.c | 118 ++++++++++++++++++++++++++++++++++++ > commit-reach.h | 17 ++++++ > ref-filter.c | 78 +++++++++++++++++++++++- > ref-filter.h | 15 +++++ > t/helper/test-reach.c | 2 + > t/perf/p1500-graph-walks.sh | 31 ++++++++++ > t/t6600-test-reach.sh | 94 ++++++++++++++++++++++++++++ > 7 files changed, 354 insertions(+), 1 deletion(-)
I was expecting to see an documentation update to for-each-ref (and probably branch and tag) so that what this new atom means. Is it that %(is-base:<commit>) interpolates to <commit> for a ref that is an ancestor of <commit>, and interpolates to an empty string for a ref that is not, or something?
Thanks.