From: Daniel Gustafsson <daniel@yesql.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix some trailing whitespace in documentation files
Date: Tue, 19 Apr 2022 20:57:23 +0200
Message-ID: <1A5D1665-86ED-4A96-A552-C7207CD5CF90@yesql.se> (raw)
In-Reply-To: <2548443.1650378244@sss.pgh.pa.us>
References: <E1nfcV1-000kOR-E5@gemulon.postgresql.org>
<2021248.1650140817@sss.pgh.pa.us>
<90abc132-ab5a-cbef-b330-8d58c24e4c6c@enterprisedb.com>
<2548443.1650378244@sss.pgh.pa.us>
> On 19 Apr 2022, at 16:24, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It's bothered the neatnik in me for a long time, so I'm happy to
> make it happen if there are not objections.
Mildly on-topic: Has the topic of a pgindent like process for docs been
discussed at some point? The archives didn't turn up anything for me.
--
Daniel Gustafsson https://vmware.com/
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: daniel@yesql.se, tgl@sss.pgh.pa.us, peter.eisentraut@enterprisedb.com
Subject: Re: pgsql: Fix some trailing whitespace in documentation files
In-Reply-To: <1A5D1665-86ED-4A96-A552-C7207CD5CF90@yesql.se>
References: <E1nfcV1-000kOR-E5@gemulon.postgresql.org> <2021248.1650140817@sss.pgh.pa.us> <90abc132-ab5a-cbef-b330-8d58c24e4c6c@enterprisedb.com> <2548443.1650378244@sss.pgh.pa.us> <1A5D1665-86ED-4A96-A552-C7207CD5CF90@yesql.se>
* 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