I merged your branch and declared the result stable for Pharo 3: === Name: Glorp-SvenVanCaekenberghe.89 Author: SvenVanCaekenberghe Time: 2 September 2014, 5:08:03.507586 pm UUID: 5c4bda4a-9395-4015-b388-c8ce00b65e19 Ancestors: Glorp-MarianoMartinezPeck.88, Glorp-EstebanMaringolo.87
Merging with Esteban Maringolo's branch: adding a #dataAndTime PostgreSQL type for Pharo === Name: ConfigurationOfGlorp-SvenVanCaekenberghe.38 Author: SvenVanCaekenberghe Time: 2 September 2014, 5:12:20.404014 pm UUID: a8d54504-7a5a-4a43-92cd-3d66b252611e Ancestors: ConfigurationOfGlorp-EstebanMaringolo.37 Moved to #stable 1.7 for Pharo 3+ === On 01 Sep 2014, at 08:06, Sven Van Caekenberghe <[email protected]> wrote: > > On 01 Sep 2014, at 00:21, Esteban A. Maringolo <[email protected]> wrote: > >> Yes... it was intentional. > > OK, but what about the second part, about it being non-intrusive ? > >> Because there is no "official" maintainer of the GLORP package, I >> didn't want to add stuff to the main codebase. Same story as with the >> PostgresV2 package. >> >> Regards! >> >> Esteban A. Maringolo >> >> >> 2014-08-31 19:16 GMT-03:00 Sven Van Caekenberghe <[email protected]>: >>> >>> On 31 Aug 2014, at 12:27, Sven Van Caekenberghe <[email protected]> wrote: >>> >>>>> ps: There is also other versions of GLORP I didn't bless as #stable. >>>> >>>> That seems a bit more complicated: the Glorp ancestry is mixed up, we >>>> should merge this carefully: >>>> >>>> you made versions 86 & 87 while those already existed, the latest 88 skips >>>> your version. >>>> >>>> in any case, 88 now works for me, but I fear it skips your code >>> >>> Ah, I see, this was an intentional branch, right ? >>> >>> Anyway, your addition seems non-intrusive, since it only adds a type, which >>> does not get used unless one specifically asks for it, correct ? >>> >>> If so, I can merge this, commit a new version and update the config. >>> >>> Sven >> >
