From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: PDF docs build: avoid spurious "warn" in build logs.
Date: Sat, 08 Feb 2025 03:14:12 +0000
Message-ID: <E1tgbIK-005xmX-6D@gemulon.postgresql.org> (raw)
PDF docs build: avoid spurious "warn" in build logs.
Improve on e4c886519 so that the string "warn" appears in
the output when there's a problem, and not when there isn't.
This should silence noise I've been seeing in my buildfarm
warning scraper.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/ecb8226af63dc8f1c0859977102764704368693b
Modified Files
--------------
doc/src/sgml/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: PDF docs build: avoid spurious "warn" in build logs.
In-Reply-To: <E1tgbIK-005xmX-6D@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox