Re: [DOCS] Sync rep doc corrections - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [DOCS] Sync rep doc corrections
Date
Msg-id 9160.1299521791@sss.pgh.pa.us
Whole thread Raw
In response to Re: [DOCS] Sync rep doc corrections  (Thom Brown <thom@linux.com>)
Responses Re: [DOCS] Sync rep doc corrections
List pgsql-hackers
Thom Brown <thom@linux.com> writes:
> On 7 March 2011 23:21, David Fetter <david@fetter.org> wrote:
>> As I'm putting together the patches section for the PostgreSQL Weekly
>> News, it helps me *enormously* to have only one list I need to check,
>> so at least for me, it's an enormous help to have all patches at least
>> CC'd, or better still, only posted, to -hackers.

I'm not certain that David's convenience should be the exclusive
consideration when deciding what goes where ;-)

> I cross-posted as it's a docs change, but I want to invite the
> critical eye of those who dev'd it.  Okay, so doc patches should go
> exclusively to the -hackers list?  Last time I recall some disparity
> surrounding what I should be doing.

If we do that then it becomes worth wondering what the -docs list is for
at all.  Maybe we *should* get rid of it; I dunno.  I see your point
about how the factual issues involved in a docs change ought to be
vetted on -hackers, but on the other hand the traffic on -hackers is so
high already that I'm not happy about folding another list with a
reasonably distinct charter into it.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: How should the primary behave when the sync standby goes away? Re: Sync Rep v17
Next
From: Thom Brown
Date:
Subject: Re: [DOCS] Column-level trigger doc typo fix