Re: pgsql: pg_upgrade: document possible pg_hba.conf options

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: pg_upgrade: document possible pg_hba.conf options
Date: 2013-07-11 21:59:35
Message-ID: 1275.1373579975@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Jul 11, 2013 at 12:13:10PM -0400, Alvaro Herrera wrote:
>> Standard operating procedure everyone follos is that you should post the
>> patch to -hackers first, wait a couple of hours for any possible input,
>> push the commit, then reply to the original -hackers thread stating you
>> have committed it.

> I don't think we need that formality with a doc patch. I don't see
> others doing that.

I've always thought that a "patch applied" followup mail was a waste of
time and readers' attention. Anybody who cares about that will know it
was applied because they're watching pgsql-committers or the git feed.

I do think it's sometimes polite to follow up that way to a bug
submitter, or if the discussion was in some other non-hackers list,
because then the audience might not be following commits. But I don't
think it's particularly useful in pgsql-hackers threads.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2013-07-11 22:27:53 Re: pgsql: pg_upgrade: document possible pg_hba.conf options
Previous Message Bruce Momjian 2013-07-11 21:48:55 Re: pgsql: pg_upgrade: document possible pg_hba.conf options