On 3/10/17 14:53, Jim Nasby wrote: > The biggest win we'd get from something like Travis would be if the > commitfest monitored for new patch files coming in for monitored threads > and it created a new branch, applied the patches, and if they applied > without error commit the branch and push to let Travis do it's thing. We > wouldn't want that running in the main git repo, but it should be fine > in a fork that's dedicated to that purpose.
This has been discussed several times before, e.g., https://www.postgresql.org/message-id/54dd2413.8030...@gmx.net -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
