Subject: Re: [PATCH v3 0/2] Add new "describe" atom

From: Junio C Hamano <[email-masked]>
Date: Thu, 20 Jul 2023 15:52:12 -0700

Kousik Sanagavarapu <[email-masked]> writes:

> PATCH 1/2 - Left unchanged expect for small changes in the commit
> 	    message for more clarity.
>
> PATCH 2/2 - We now parse the arguments in a seperate function
> 	    `describe_atom_option_parser()` call this in
> 	    `describe_atom_parser()` instead to populate
> 	    `atom->u.describe_args`. This splitting of the function
> 	    helps err at the right places.

This topic may be getting rerolled but from the CI logs,
comparing 

 * https://github.com/git/git/actions/runs/5603242871 (seen at
   77ba682) that passes the tests

 * https://github.com/git/git/actions/runs/5605480104 (seen at
   29f0316) that breaks linux-gcc (ubuntu-20.04) at t6300 [*]

output from "git shortlog --no-merges 77ba682..29f0316" [*] makes us
suspect that this topic may be the culprit of the recent breakage.

The linux-gcc job is where we force the initial branch name to be
'main' and not 'master', so if your tests assume that the initial &
primary branch name is 'master', that may be something you need to
fix.

Thanks.

[Reference]
 * https://github.com/git/git/actions/runs/5605480104/job/15186229680

 * git shortlog --no-merges 77ba682..29f0316
Alex Henrie (1):
      sequencer: finish parsing the todo list despite an invalid first line

Beat Bolli (1):
      trace2: fix a comment

Junio C Hamano (4):
      short help: allow multi-line opthelp
      remote: simplify "remote add --tags" help text
      short help: allow a gap smaller than USAGE_GAP
      ###

Kousik Sanagavarapu (2):
      ref-filter: add multiple-option parsing functions
      ref-filter: add new "describe" atom