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

Re: [PATCH v2 3/4] travis-ci: check AsciiDoc/AsciiDoctor stderr output

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 27, 2017, 01:21 UTC
Message-ID
<xmqqshkuprwj.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170426191545.27552-4-larsxschneider@gmail.com>
Lars Schneider <larsxschneider@gmail.com> writes:
> Ensure that nothing is written to stderr during a documentation build.

I guess we'll know if any output to stderr is an error, or if there are some informational output that would trigger failure from this change soon enough. Will queue.

Thanks.
Previous: Lars SchneiderNext: Lars Schneider
Message 5 of 6 in “travis-ci: build docs with asciidoctor”
  1. 0/4 travis-ci: build docs with asciidoctorLars Schneider, Apr 26, 2017
  2. 1/4 travis-ci: build documentation with AsciiDoc and AsciidoctorLars Schneider, Apr 26, 2017
  3. 2/4 travis-ci: parallelize documentation buildLars Schneider, Apr 26, 2017
  4. 3/4 travis-ci: check AsciiDoc/AsciiDoctor stderr outputLars Schneider, Apr 26, 2017
  5. Junio C HamanoApr 27, 2017
  6. 4/4 travis-ci: unset compiler for jobs that do not need oneLars Schneider, Apr 26, 2017

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.