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

Re: [PATCH v2 1/4] doc: add some missing technical documents

From
Ramsay Jones <ramsay@ramsayjones.plus.com>
Date
Oct 8, 2025, 22:01 UTC
Message-ID
<3286707e-8cc0-430e-a2d3-546352d50b6d@ramsayjones.plus.com>
In-Reply-To
<xmqqfrbtfcbv.fsf@gitster.g>
On 08/10/2025 8:00 pm, Junio C Hamano wrote:
Show 30 quoted lines
> 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

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 25 in “technical docs in make build”
  1. 0/4 technical docs in make buildRamsay Jones, Oct 2, 2025
  2. 1/4 doc: add some missing technical documentsRamsay Jones, Oct 2, 2025
  3. Patrick SteinhardtOct 8, 2025
  4. Junio C HamanoOct 8, 2025
  5. Ramsay JonesOct 8, 2025
  6. Junio C HamanoOct 8, 2025
  7. Ramsay JonesOct 8, 2025
  8. 2/4 doc: remembering-renames.adoc: fix asciidoc warningsRamsay Jones, Oct 2, 2025
  9. Elijah NewrenOct 8, 2025
  10. Ramsay JonesOct 8, 2025
  11. 3/4 doc: sparse-checkout.adoc: fix asciidoc warningsRamsay Jones, Oct 2, 2025
  12. Kristoffer HaugsbakkOct 7, 2025
  13. Ramsay JonesOct 7, 2025
  14. Elijah NewrenOct 8, 2025
  15. Ramsay JonesOct 8, 2025
  16. 4/4 doc: commit-graph.adoc: fix up some formattingRamsay Jones, Oct 2, 2025
  17. Ramsay JonesOct 2, 2025
  18. 0/4 technical docs in make buildRamsay Jones, Oct 16, 2025
  19. 1/4 doc: remembering-renames.adoc: fix asciidoc warningsRamsay Jones, Oct 16, 2025
  20. 2/4 doc: sparse-checkout.adoc: fix asciidoc warningsRamsay Jones, Oct 16, 2025
  21. 3/4 doc: commit-graph.adoc: fix up some formattingRamsay Jones, Oct 16, 2025
  22. 4/4 doc: add large-object-promisors.adoc to the docs buildRamsay Jones, Oct 16, 2025
  23. Ramsay JonesOct 17, 2025
  24. Junio C HamanoOct 23, 2025
  25. Ramsay JonesOct 23, 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.