| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: use of '=' in long options documentation |
| Date: | 2011-03-09 16:47:00 |
| Message-ID: | 201103091647.p29Gl1J13261@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Peter Eisentraut wrote:
> 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.
Yeah! Someone chimed in with a vote! I will update the docs, but not
adjust any summary that has a space after the equals, e.g. initdb.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-03-09 16:55:13 | Re: use of '=' in long options documentation |
| Previous Message | Bruce Momjian | 2011-03-09 16:08:58 | Re: Improve initdb and pg_controldata manual pages |