git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] for-each-ref: call --start-after argument "marker"

From
Karthik Nayak <karthik.188@gmail.com>
Date
Aug 11, 2025, 09:19 UTC
Message-ID
<CAOLa=ZQqY8MDTs846mkVsxXrmOmC5O_sv6BxUHqYjGk1Ag+Osw@mail.gmail.com>
In-Reply-To
<1a32a666-fcf4-4f05-a468-2afa07fa0e2d@web.de>
René Scharfe <l.s.r@web.de> writes:
Show 21 quoted lines
> dabecb9db2 (for-each-ref: introduce a '--start-after' option,
> 2025-07-15) added the option --start-after and referred to its argument
> as "marker" in documentation and usage string, but not in the option's
> short help.  Use "marker" there as well for consistency and brevity.
>
> Signed-off-by: René Scharfe <l.s.r@web.de>
> ---
>  builtin/for-each-ref.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/builtin/for-each-ref.c b/builtin/for-each-ref.c
> index 8b5fe7b65e..222637a2c0 100644
> --- a/builtin/for-each-ref.c
> +++ b/builtin/for-each-ref.c
> @@ -46,7 +46,7 @@ int cmd_for_each_ref(int argc,
>  		OPT_GROUP(""),
>  		OPT_INTEGER( 0 , "count", &format.array_opts.max_count, N_("show only <n> matched refs")),
>  		OPT_STRING(  0 , "format", &format.format, N_("format"), N_("format to use for the output")),
> -		OPT_STRING(  0 , "start-after", &filter.start_after, N_("start-after"), N_("start iteration after the provided marker")),
> +		OPT_STRING(  0 , "start-after", &filter.start_after, N_("marker"), N_("start iteration after the provided marker")),
>
Ah! I did fix a typo here, but your fix is better. Thanks.
Show 5 quoted lines
>  		OPT__COLOR(&format.use_color, N_("respect format colors")),
>  		OPT_REF_FILTER_EXCLUDE(&filter),
>  		OPT_REF_SORT(&sorting_options),
> --
> 2.50.1
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 8 in “for-each-ref: call --start-after argument "marker"”
  1. for-each-ref: call --start-after argument "marker"René Scharfe, Aug 9, 2025
  2. Junio C HamanoAug 10, 2025
  3. Karthik NayakAug 11, 2025
  4. Junio C HamanoAug 11, 2025
  5. Karthik NayakAug 12, 2025
  6. Junio C HamanoAug 12, 2025
  7. Karthik NayakAug 12, 2025
  8. Junio C HamanoAug 12, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.