Applied.
---
Bruce Momjian wrote:
> Kevin Grittner wrote:
> > Bruce Momjian wrote:
> > > Peter Eisentraut wrote:
> > >> On tis, 2011-03-08 at 22:32 -0500, Bruce Momjian wrote:
> > >>> Looking at our ref pages, I see some ma
Kevin Grittner wrote:
> Bruce Momjian wrote:
> > 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
>
Bruce Momjian wrote:
> 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_du
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:
> >
> > --l
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 u
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?
--
Bruce Momjian http://momjian.us
E