Re: pgsql-patches considered harmful

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, Greg Stark <gsstark(at)mit(dot)edu>
Subject: Re: pgsql-patches considered harmful
Date: 2006-07-11 16:17:10
Message-ID: 878xn0nmk9.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Andrew Dunstan <andrew(at)dunslane(dot)net> writes:

> Marc G. Fournier wrote:
> >
> > If nobody objects within, say, the next 24 hours ... ? I'll enabled that one
> > both ...
>
> Don't be surprised if there are objections - this is one of those things like
> emacs vs vi that stirs up religious debate.

Indeed. The usual issue is that if someone hits "personal reply" their
personal note to the author will go to the mailing list. Some lists have
problems with people sending personal replies inappropriately but I doubt
that's the case for -patches or -committers.

I have the additional complaint that this doesn't actually solve most of my
original complaints and might reduce the pressure to find a better solution.
The patches announcements themselves would still be basically invisible within
the community.

Even if someone isn't going to read or apply the actual patch I think there is
an enormous benefit to be gained from having everyone at least know it went
by. Much as I'm sure not everyone reads every line of every message on
-hackers but they are aware of what topics are under discussion.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2006-07-11 16:50:38 Re: Three weeks left until feature freeze
Previous Message Steve Singer 2006-07-11 15:59:31 Re: More nuclear options