Dave Page wrote:
You should post into -patches@ list, then some core member will
review and apply it.
Not core, a committer. Although some people are both, not all are. If
that makes sense!
I have raised this issue before: I don't believe committers are
identified as such on th
Tom Lane wrote:
Joshua Reich <[EMAIL PROTECTED]> writes:
Do we have an active maintainer of this code?
It sounds like you've just acquired that position ;-)
More than happy to take the role.
How is it reviewed?
Same as everything else, pretty much: patches go to pgsql-patches and
are (
On 7/19/06, Dave Page wrote:
> You should post into -patches@ list, then some core member will
> review and apply it.
Not core, a committer. Although some people are both, not all are. If
that makes sense!
Indeed.
Obviously, non-committers can (and do) review patches. Just you need
to get t
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Marko Kreen
> Sent: 19 July 2006 16:13
> To: Joshua Reich
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch process?
>
> On 7/19/06, Joshua Reich <[EMA
Joshua Reich <[EMAIL PROTECTED]> writes:
> Just a general question - I submitted a patch for contrib/cube (adding a
> new function & converting everything from V0 to V1), what is the process
> from here onwards? Do we have an active maintainer of this code?
It sounds like you've just acquired th
On 7/19/06, Joshua Reich <[EMAIL PROTECTED]> wrote:
Just a general question - I submitted a patch for contrib/cube (adding a
new function & converting everything from V0 to V1), what is the process
from here onwards? Do we have an active maintainer of this code? How is
it reviewed?
You should p
Just a general question - I submitted a patch for contrib/cube (adding a
new function & converting everything from V0 to V1), what is the process
from here onwards? Do we have an active maintainer of this code? How is
it reviewed?
I would like to continue working on the cube stuff, as our comp
