From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: use of '=' in long options documentation
Date: Wed, 09 Mar 2011 17:44:03 +0200
Message-ID: <1299685443.20647.4.camel@fsopti579.F-Secure.com> (raw)
In-Reply-To: <201103090332.p293Wcq27270@momjian.us>
References: <201103090332.p293Wcq27270@momjian.us>
On tis, 2011-03-08 at 22:32 -0500, Bruce Momjian wrote:
> Looking at our ref pages, I see some manual pages specify long options
> that take arguments using '=', e.g. initdb.sgml:
>
> --long-opt=opt
>
> and some do not, e.g. pg_dump.sgml:
>
> --long-opt opt
>
> So, which should we use, for consistency?
Using = is more common usage, I think.
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-docs@postgresql.org
Cc: peter_e@gmx.net, bruce@momjian.us
Subject: Re: use of '=' in long options documentation
In-Reply-To: <1299685443.20647.4.camel@fsopti579.F-Secure.com>
* 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