From: Ramsay Jones <ramsay@ramsayjones•plus.com>
To: Junio C Hamano <gitster@pobox•com>, Patrick Steinhardt <ps@pks•im>
Cc: GIT Mailing-list <git@vger•kernel.org>,
Elijah Newren <newren@gmail•com>,
Derrick Stolee <stolee@gmail•com>
Subject: Re: [PATCH v2 1/4] doc: add some missing technical documents
Date: Wed, 8 Oct 2025 23:01:18 +0100 [thread overview]
Message-ID: <3286707e-8cc0-430e-a2d3-546352d50b6d@ramsayjones.plus.com> (raw)
In-Reply-To: <xmqqfrbtfcbv.fsf@gitster.g>
On 08/10/2025 8:00 pm, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks•im> writes:
>
>> This builds on our existing linting rule and would catch any discrepancy
>> in man pages that we have in "Documentation/technical/" that isn't
>> listed in Meson.
>
> Yeah, I remember the existing check helping me spot potential issues
> in a series or two.
>
>> But regardless of that, the above check surfaces one more missing
>> article:
>>
>> $ make lint-docs-meson
>> GEN doc.dep
>> make: *** Deleting file 'doc.dep'
>> tmp-meson-diff/meson.adoc tmp-meson-diff/actual.adoc differ: byte 3877, line 206
>> Meson man pages differ from actual man pages:
>> --- tmp-meson-diff/meson.adoc 2025-10-08 08:42:49.864991169 +0200
>> +++ tmp-meson-diff/actual.adoc 2025-10-08 08:42:50.072988794 +0200
>> @@ -203,6 +203,7 @@
>> git-worktree.adoc
>> git-write-tree.adoc
>> hash-function-transition.adoc
>> +large-object-promisors.adoc
>> long-running-process-protocol.adoc
>> multi-pack-index.adoc
>> packfile-uri.adoc
>> make: *** [Makefile:526: lint-docs-meson] Error 1
>
> Good. I'll expect Ramsay will handle this one in v3?
OK, will do.
Since patch #1 is already in 'next', do I effectively create a new
patch series out of patches #2->#4, plus this new patch?
ATB,
Ramsay Jones
next prev parent reply other threads:[~2025-10-08 22:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://lore.kernel.org/git/bcb3b3a3-bb13-4808-9363-442b5f9be05f@ramsayjones.plus.com/>
2025-10-02 22:12 ` [PATCH v2 0/4] technical docs in make build Ramsay Jones
2025-10-02 22:12 ` [PATCH v2 1/4] doc: add some missing technical documents Ramsay Jones
2025-10-08 6:45 ` Patrick Steinhardt
2025-10-08 19:00 ` Junio C Hamano
2025-10-08 22:01 ` Ramsay Jones [this message]
2025-10-08 22:33 ` Junio C Hamano
2025-10-08 21:56 ` Ramsay Jones
2025-10-02 22:12 ` [PATCH v2 2/4] doc: remembering-renames.adoc: fix asciidoc warnings Ramsay Jones
2025-10-08 3:51 ` Elijah Newren
2025-10-08 21:38 ` Ramsay Jones
2025-10-02 22:12 ` [PATCH v2 3/4] doc: sparse-checkout.adoc: " Ramsay Jones
2025-10-07 12:20 ` Kristoffer Haugsbakk
2025-10-07 22:17 ` Ramsay Jones
2025-10-08 3:57 ` Elijah Newren
2025-10-08 21:54 ` Ramsay Jones
2025-10-02 22:12 ` [PATCH v2 4/4] doc: commit-graph.adoc: fix up some formatting Ramsay Jones
2025-10-02 22:38 ` [PATCH v2 0/4] technical docs in make build Ramsay Jones
2025-10-16 20:02 ` [PATCH v3 " Ramsay Jones
2025-10-16 20:02 ` [PATCH v3 1/4] doc: remembering-renames.adoc: fix asciidoc warnings Ramsay Jones
2025-10-16 20:02 ` [PATCH v3 2/4] doc: sparse-checkout.adoc: " Ramsay Jones
2025-10-16 20:03 ` [PATCH v3 3/4] doc: commit-graph.adoc: fix up some formatting Ramsay Jones
2025-10-16 20:03 ` [PATCH v3 4/4] doc: add large-object-promisors.adoc to the docs build Ramsay Jones
2025-10-17 16:37 ` Ramsay Jones
2025-10-23 19:33 ` [PATCH v3 0/4] technical docs in make build Junio C Hamano
2025-10-23 20:06 ` Ramsay Jones
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3286707e-8cc0-430e-a2d3-546352d50b6d@ramsayjones.plus.com \
--to=ramsay@ramsayjones$(echo .)plus.com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=newren@gmail$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=stolee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox