Re: [PATCH v4 0/4] for-each-ref: introduce seeking functionality via '--start-after'
- From
Karthik Nayak <karthik.188@gmail.com>
- Date
- Jul 15, 2025, 09:49 UTC
- Message-ID
- <CAOLa=ZRT70g90+e-Mhy_USaXqLpDVamRm5dXc-r_fF2PHPQyPw@mail.gmail.com>
- In-Reply-To
- <xmqqms96u38z.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 19 quoted lines
> Christian Couder <christian.couder@gmail.com> writes: > >> On Fri, Jul 11, 2025 at 6:20 PM Karthik Nayak <karthik.188@gmail.com> wrote: >> >>> Initially I was also planning to cleanup all the `refs_for_each...()` >>> functions in 'refs.h' by simply using the iterator, but this bloated the >>> series. So I've left that for another day. >> >> I wonder if there is a plan to add the '--start-after' option to `git >> branch` and `git tag` too? > > Good question. > > "git for-each-ref" is for scripters, "git branch/tag" are for > humans. And humans do not page (outside "more/less"). > > So while it may be trivial to expose the feature to these Porcelain > commands, it is not obvious that it is a good idea worth cluttering > "git tag -h" output.
Agreed, since the functionality is built into 'ref-filter', it should be easy to expand to these commands. But I don't see the need for it.
Karthik