Re: GIT move - Mailing list pgsql-jdbc

From Maciek Sakrejda
Subject Re: GIT move
Date
Msg-id CAH_hXRa7D8CCDpGhZHmLtXf0ayXObq06vJJORRhf_pV+v+jj-w@mail.gmail.com
Whole thread Raw
In response to Re: GIT move  (Kris Jurka <books@ejurka.com>)
Responses Re: GIT move  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
>> 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.

---
Maciek Sakrejda | System Architect | Truviso

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

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: GIT move
Next
From: Dave Cramer
Date:
Subject: Re: GIT move