From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How to submit a patch |
Date: | 2008-04-16 20:36:13 |
Message-ID: | 4806633D.4030604@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Merlin Moncure wrote:
> I've been mostly following this discussion on
> this particular topic but have absolutely no idea what, if anything,
> to do on the wiki in terms of submitting patch.
>
I think the short answer right now to this and to Joshua's original
question is: to submit a patch do what has always been done, i.e. send
the patch to the mailing list. You can also add the patch to the list on
the wiki, but if you don't, it won't be forgotten.
All the rest is for reviewers/committers.
I've been wondering idly and probably pointlessly if we should try
adopting something like the methodology of the Usenet Oracle, which, if
you ask it a question will usually send you one to answer in return.
Obviously we can't always do that, but maybe we should be asking people
who are obviously competent enough (judging by the quality and
complexity of the patches they submit) to step up to the plate more on
reviewing patches. No amount of process will substitute for more reviewers.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2008-04-16 20:49:03 | Re: Timely reporting of COPY errors |
Previous Message | Martijn van Oosterhout | 2008-04-16 20:29:07 | Timely reporting of COPY errors |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2008-04-16 23:02:06 | Re: How to submit a patch |
Previous Message | Joshua D. Drake | 2008-04-16 20:21:10 | Re: How to submit a patch |