From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: About that CommitFest redirect page ... |
Date: | 2008-09-07 22:29:48 |
Message-ID: | 87ljy3y4gz.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> The use case for adding things to the next commitfest while a commitfest is
> currently happening much less convincing. Why would you submit a patch now
> when you still have two months to work on on it and you should be reviewing
> other patches anyway?
Same reason you would send in a patch any other time, because you have a
question and/or want feedback.
Nonetheless I agree that the link to the currently active commitfest is the
one most people would want most of the time. There's a link at the top of the
active commitfest to the currently open commitfest which makes it clear when
to use which.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-09-07 22:39:28 | Re: Proposed patch: make pg_dump --data-only consider FK constraints |
Previous Message | Alvaro Herrera | 2008-09-07 21:43:36 | Re: Move src/tools/backend/ to wiki |