| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest 2018-07 |
| Date: | 2018-06-05 22:41:00 |
| Message-ID: | 20180605224100.GC1442@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 05, 2018 at 11:20:57AM -0400, Peter Eisentraut wrote:
> On 6/5/18 09:12, Andres Freund wrote:
>> I'd rather create a new 2018-07, and just manually move old patches to
>> it.
>
> My concern is whether the commitfest app will handle that well. There
> is no "move to previous commit fest" button. So you'd have to do it in
> some evil way, possibly confusing the continuity of the patch records.
> There might be other issues of this sort. I don't think this use case
> is fully worked out.
Yeah, that's the point I just raised before seeing this email. Renaming
is just going to be more simple at the end.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-06-05 23:03:23 | Re: libpq compression |
| Previous Message | Magnus Hagander | 2018-06-05 22:38:56 | Re: commitfest 2018-07 |