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: 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-07 00:50:09
Message-ID: CADK3HHKYDeTfekAKcZFnjs6n5H15eGeZ6fuR38LNF9yeUvP5Xw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
On Mon, Feb 6, 2012 at 7:47 PM, Maciek Sakrejda <msakrejda(at)truviso(dot)com> wrote:
>>> Did this happen ?
>>>
>>
>> Not completely.  I'm most of the way through it, but was not able to
>> finish last night.  I will complete the move today.
>
> Great to hear; please let me know if you hit any issues with the
> transition scripts.
>
> Also, vaguely on this topic, I'm not sure if there's a formal plan for
> methods of accepting patches (e.g., via github pull requests), but I
> highly recommend that all patches be required to be rebased against
> trunk/master, resulting in fast-forward merges into the main tree.
> This makes history much simpler to follow (no merge nodes) without a
> significant downside.
>

Currently the main project still requires a context patch as well


Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

In response to

Responses

pgsql-jdbc by date

Next:From: Maciek SakrejdaDate: 2012-02-07 00:57:20
Subject: Re: GIT move
Previous:From: Maciek SakrejdaDate: 2012-02-07 00:47:27
Subject: Re: GIT move

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