Re: [PATCH] cmd-list.perl: fix identifying man sections

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Sep 26, 2022, 13:35 UTC
Message-ID: <220926.86czbi1cj2.gmgdl@evledraar.gmail.com>
In-Reply-To: <Yy4uDW9YjpleFUHW@coredump.intra.peff.net>

On Fri, Sep 23 2022, Jeff King wrote:

Show 24 quoted lines

> On Fri, Sep 23, 2022 at 09:03:34AM +0200, Martin Ågren wrote:
>
>> This makes our git(1) manpage look as follows:
>> 
>>   Main porcelain commands
>>        git-add(git)
>>            Add file contents to the index.
>> 
>>   [...]
>> 
>>        gitk(git)
>>            The Git repository browser.
>> 
>>        scalar(scalar)
>>            A tool for managing large Git repositories.
>
> Good catch. The patch looks good (I was going to suggest ?:, but I see
> Ævar beat me to it).
>
> I wondered if we might have caught this in a more automatic way. The
> output of:
>
>   cd Documentation
>   ./doc-diff cc75e556a9^ cc75e556a9

FWIW I asked before on-list[1] why the CI output of https://github.com/gitster/git wasn't visible, I don't know if it's a setting Junio can adjust, or something else.

I wanted to set something up to scrape the WC E-Mails, and see what the CI status of those topics was individually.

And, if others found it useful eventually, perhaps send that as a follow-up to the list. I.e. if CI for the topic passes, what (if any) the output differences are. We could then just run a "doc-diff" in the CI, and report (as part of some matrix) a checkmark next to those that have doc changes.

Of course I could re-push all of the topics myself, but that would take a long time to complete, and compete with any other use I have for CI myself. So piggy-backing on gitster's would be much better, if they're even there in the first place...

1. https://lore.kernel.org/git/220114.86fspqrxbw.gmgdl@evledraar.gmail.com/