| From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Brendan Jurd" <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Marko Kreen" <markokr(at)gmail(dot)com> |
| Subject: | Re: CommitFest rules |
| Date: | 2008-07-10 14:28:35 |
| Message-ID: | 937d27e10807100728h191eb05cxaf94cd2e71efc10a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 10, 2008 at 3:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I surely do not have an objection to having a link defined as above ---
> I just wanted to be clear on what we meant by "current commitfest".
> We probably need two separate terms for "the place to submit new
> patches" and "the place we are trying to commit patches from".
Well we have two separate links now, with hints as to their usage:
# Upcoming CommitFest - add new patches here
# In-progress CommitFest - patch review underway here
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-07-10 14:30:42 | Re: Protocol 3, Execute, maxrows to return, impact? |
| Previous Message | Tom Lane | 2008-07-10 14:22:28 | Re: Protocol 3, Execute, maxrows to return, impact? |