Re: GIT move

From: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, Andreas Joseph Krogh <andreak(at)officenet(dot)no>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: GIT move
Date: 2012-02-08 06:39:46
Message-ID: CAH_hXRb5fp9S_nfKkQ5za43XqP-DQuo-9nynXeMOtMnKY4o0xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

>> As far as I
>> can tell, the reason the main project requires patches was to change
>> the *process* as little as possible in the course of changing the VCS
>> plumbing.
>
> That's *a* reason, but not the only one. Other large considerations are
> that we consider that the act of submitting the patch to the mailing
> list is evidence of intent to license the code under the Postgres
> license, and further that this evidence is archived in the PG list
> archives.

That's an excellent point--thanks for the clarification.
---
Maciek Sakrejda | System Architect | Truviso

1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2012-02-08 12:27:45 Re: GIT move
Previous Message Tom Lane 2012-02-08 03:34:34 Re: GIT move