| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Jeremy Schneider <schnjere(at)amazon(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, "Nasby, Jim" <nasbyj(at)amazon(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Maliing list request: pgsql-forks@ |
| Date: | 2019-08-08 17:57:07 |
| Message-ID: | 59546C13-75F0-46F7-A0D1-D41B153D57D0@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> On Aug 8, 2019, at 10:55, Jeremy Schneider <schnjere(at)amazon(dot)com> wrote:
> There's a significant difference between the idea of people forking PostgreSQL code and the idea of downstream builds that are supplementing PostgreSQL capabilities but regularly merging from upstream (even if they aren't presently able to package as extensions).
I think that's a distinction without a difference. Most "forks" these days (unless we're talking about ones that are very historical) merge regularly from upstream.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2019-08-08 21:38:17 | Re: Maliing list request: pgsql-forks@ |
| Previous Message | Jeremy Schneider | 2019-08-08 17:55:07 | Re: Maliing list request: pgsql-forks@ |