Skip site navigation (1) Skip section navigation (2)

Re: GIT move

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 12:27:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
I for one would like to keep the policy that we require a context
patch to be sent to the list.
Having to chase down everyone's git repo seems like more work rather than less

Dave Cramer


On Wed, Feb 8, 2012 at 1:39 AM, Maciek Sakrejda <msakrejda(at)truviso(dot)com> wrote:
>>> 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
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:

In response to


  • Re: GIT move at 2012-02-08 12:40:26 from Vitalii Tymchyshyn

pgsql-jdbc by date

Next:From: Vitalii TymchyshynDate: 2012-02-08 12:40:26
Subject: Re: GIT move
Previous:From: Maciek SakrejdaDate: 2012-02-08 06:39:46
Subject: Re: GIT move

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group