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

Re: [PATCH v4 1/2] Documentation: fix linkgit references

From
Jeff King <peff@peff.net>
Date
May 4, 2016, 21:44 UTC
Message-ID
<20160504214412.GA25237@sigill.intra.peff.net>
In-Reply-To
<xmqq4madfqxs.fsf@gitster.mtv.corp.google.com>
On Wed, May 04, 2016 at 02:34:23PM -0700, Junio C Hamano wrote:
Show 20 quoted lines
> Third time's a charm, perhaps?
>  
> -- >8 --
> Subject: [PATCH] ci: validate "gitlink:" in documentation
> 
> It is easy to add incorrect "linkgit:<page>[<section>]" references
> to our documentation suite.  Catch these common classes of errors:
> 
>  * Referring to Documentation/<page>.txt that does not exist.
> 
>  * Referring to a <page> outside the Git suite.  In general, <page>
>    must begin with "git".
> 
>  * Listing the manual <section> incorrectly.  The first line of the
>    Documentation/<page>.txt must end with "(<section>)".
> 
> with a new script "ci/lint-gitlink", and drive it from "make check-docs".
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
This looks good to me. Two minor nits that may not be worth addressing:
> +lint-docs::
> +	$(QUIET_LINT)$(foreach txt,$(patsubst %.html,%.txt,$(DOC_HTML)), \
> +	../ci/lint-gitlink $(txt))
> +
This dependency feels funny. Wouldn't CI want to invoke this as:
  make -C Documentation lint-docs

IOW, Documentation owns the script (just like t/ owns its own lint scripts like check-non-portable-shell.pl), and CI always just triggers the make-driven checks, just as a normal developer would?

Show 12 quoted lines
> +sub lint {
> +	my ($file) = @_;
> +	open my $fh, "<", $file
> +		or return;
> +	while (<$fh>) {
> +		my $where = "$file:$.";
> [... actual linting of line ...]
> +}
> +
> +for (@ARGV) {
> +	lint($_);
> +}
The usual perl way here would be:
  while(<>) {
	my $where = "$ARGV:$.";
	... actual linting of line ...
  }

where "<>" automagically reads from files on the command-line or stdin if none were specified (and sets $ARGV as appropriate). But maybe you prefer not to handle the stdin case (it is a benefit sometimes, but an annoyance if you accidentally end up with an empty file list).

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 31 of 53 in “travis-ci: build documentation”
  1. travis-ci: build documentationlarsxschneider@gmail.com, Apr 29, 2016
  2. Jeff KingApr 29, 2016
  3. Matthieu MoyApr 29, 2016
  4. Lars SchneiderApr 29, 2016
  5. Jeff KingApr 29, 2016
  6. Stefan BellerApr 29, 2016
  7. Matthieu MoyApr 29, 2016
  8. Lars SchneiderApr 29, 2016
  9. Junio C HamanoApr 29, 2016
  10. 0/2 travis-ci: build documentationlarsxschneider@gmail.com, May 2, 2016
  11. 1/2 Documentation: fix linkgit referenceslarsxschneider@gmail.com, May 2, 2016
  12. Jeff KingMay 2, 2016
  13. Lars SchneiderMay 3, 2016
  14. Junio C HamanoMay 3, 2016
  15. Jeff KingMay 3, 2016
  16. Jeff KingMay 3, 2016
  17. 0/2 travis-ci: build documentationlarsxschneider@gmail.com, May 4, 2016
  18. 1/2 Documentation: fix linkgit referenceslarsxschneider@gmail.com, May 4, 2016
  19. Lars SchneiderMay 4, 2016
  20. Jeff KingMay 4, 2016
  21. Ramsay JonesMay 4, 2016
  22. Junio C HamanoMay 4, 2016
  23. Junio C HamanoMay 4, 2016
  24. Junio C HamanoMay 4, 2016
  25. Jeff KingMay 4, 2016
  26. Junio C HamanoMay 4, 2016
  27. Jeff KingMay 4, 2016
  28. Junio C HamanoMay 4, 2016
  29. Jeff KingMay 4, 2016
  30. Junio C HamanoMay 4, 2016
  31. Jeff KingMay 4, 2016
  32. Junio C HamanoMay 4, 2016
  33. Jeff KingMay 4, 2016
  34. Junio C HamanoMay 4, 2016
  35. Junio C HamanoMay 4, 2016
  36. Junio C HamanoMay 4, 2016
  37. Jeff KingMay 4, 2016
  38. Jeff KingMay 4, 2016
  39. Ævar Arnfjörð BjarmasonMay 4, 2016
  40. Jeff KingMay 4, 2016
  41. 2/2 travis-ci: build documentationlarsxschneider@gmail.com, May 4, 2016
  42. Junio C HamanoMay 10, 2016
  43. Lars SchneiderMay 13, 2016
  44. 2/2 travis-ci: build documentationlarsxschneider@gmail.com, May 2, 2016
  45. Junio C HamanoMay 2, 2016
  46. Lars SchneiderMay 3, 2016
  47. Junio C HamanoMay 3, 2016
  48. Lars SchneiderMay 4, 2016
  49. Eric WongMay 4, 2016
  50. Junio C HamanoMay 4, 2016
  51. Christian CouderMay 4, 2016
  52. Matthieu MoyMay 4, 2016
  53. Matthieu MoyApr 29, 2016

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.