| From: | Jim Nasby <jim(dot)nasby(at)openscg(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Need a builtin way to run all tests faster manner |
| Date: | 2017-03-11 20:13:09 |
| Message-ID: | 640605d6-83ed-fbe9-56f1-87cc8bd746ba@openscg.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/11/17 2:06 PM, Tom Lane wrote:
> Jim Nasby <jim(dot)nasby(at)openscg(dot)com> writes:
>> It's actually a lot harder to mess up providing a git repo link than
>> manually submitting patches to the mailing list.
> Yeah, we've heard that proposal before. We're still not doing it though.
> Insisting on patches being actually submitted to the mailing list is
> important for archival and possibly legal reasons. If someone sends
> in a link to $random-repo, once that site goes away there's no way to
> determine exactly what was submitted.
The full proposal was that the commitfest app have the ability to
generate and post the patch for you, assuming that the smoke-test passes.
--
Jim Nasby, Chief Data Architect, OpenSCG
http://OpenSCG.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2017-03-11 20:24:29 | Re: [GSOC 17] Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions |
| Previous Message | Tom Lane | 2017-03-11 20:06:47 | Re: Need a builtin way to run all tests faster manner |