Re: pgsql-patches reply-to (was Re: [PATCHES] selecting - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pgsql-patches reply-to (was Re: [PATCHES] selecting
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0FB3D@algol.sollentuna.se
Whole thread Raw
In response to Re: pgsql-patches reply-to (was Re: [PATCHES] selecting  (Steve Atkins <steve@blighty.com>)
List pgsql-hackers
> >>> I'd vote for reverting to the old way. Anyone serious
> about hacking
> >>> should be on both lists.
> >
> > Then why bother with two different lists?
> >
> > If developers need to be on both list (which I beleive they
> do), and
> > the focus of both lists is developers, then why not just
> remove one of
> > them and get rid of the problem?
>
> One reason might be that a lot of application developers who
> develop applications or modules associated with PG, but not
> the core PG code itself also lurk on -hackers, as it's by far
> the best way to keep up with the status of various PG
> enhancements (and also an excellent place to pick up a lot of
> undocumented good practices).

Won't you learn even more good practices if you actually see the patches
as well? :-P

The bottom line is, I think, does the volume of mail on -patches
actually make a big difference given the much higher volume on -hackers?
(If you just want to skip the patches, just set up attachment filtering
on the list..)

//Magnus


pgsql-hackers by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: Re: Autovacuum on by default?
Next
From: Bruce Momjian
Date:
Subject: Improvement for logging bind parameters