Re: knngist patch support

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, tomas(at)tuxteam(dot)de, Teodor Sigaev <teodor(at)sigaev(dot)ru>, "Ragi Y(dot) Burhum" <rburhum(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: knngist patch support
Date: 2010-02-11 15:23:10
Message-ID: Pine.LNX.4.64.1002111819180.16860@sn.sai.msu.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 11 Feb 2010, Greg Stark wrote:

> On Thu, Feb 11, 2010 at 1:18 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>>> In my understanding
>>> this was always enough to submit code. User's documentation is depend on
>>> discussion and review and can be added later
>>> before releasing beta.
>>
>> Several people have said this lately, but it doesn't match what I've
>> seen of our practice over the last year and a half;
>
> Perhaps the confusion is that we often say not to worry about the
> quality of the English in the documentation. That's because it's easy
> for a reviewer to fix up the English but not so easy to figure out
> what you intend the behaviour to be.

English + SGML stuff. We usually provide information in plain text, posted
in -hackers and published in my wiki. I don't remember, that there were
no information about patches.

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-02-11 15:24:20 Re: Hostnames in pg_hba.conf
Previous Message Heikki Linnakangas 2010-02-11 15:21:13 Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL