mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <>
To: Jeff King <>
Cc: "Martin Ågren" <>,, "Victoria Dye" <>,
	"Junio C Hamano" <>
Subject: Re: [PATCH] cmd-list.perl: fix identifying man sections
Date: Mon, 26 Sep 2022 15:35:06 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Sep 23 2022, Jeff King wrote:

> 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 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...


      parent reply	other threads:[~2022-09-26 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  7:03 [PATCH] cmd-list.perl: fix identifying man sections Martin Ågren
2022-09-23  7:38 ` Ævar Arnfjörð Bjarmason
2022-09-23  8:07   ` [PATCH v2] " Martin Ågren
2022-09-23  8:37     ` Ævar Arnfjörð Bjarmason
2022-09-23 11:42       ` Martin Ågren
2022-09-23 17:01     ` Junio C Hamano
2022-09-23 22:07 ` [PATCH] " Jeff King
2022-09-26  7:16   ` Martin Ågren
2022-09-26 17:06     ` Junio C Hamano
2022-09-26 13:35   ` Ævar Arnfjörð Bjarmason [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).