On 5 February 2016 at 09:16, Sandro Santilli wrote:
> Are all GEOS committers ok with moving the code from SVN
> to GIT, while keeping the current trac instance ?
+1
Best regards,
--
Mateusz Łoskot, http://mateusz.loskot.net
___
#763: Overlay operator crash
+---
Reporter: pramsey | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone: 3.5.1
Component: Default | Version: 3.5.0
Severity: Unassigned |
#766: Patch for StringTokenizer.cpp to include std::numeric
---+---
Reporter: jmckenna | Owner: geos-devel@…
Type: defect | Status: closed
Priority: major | Milestone: 3.5.1
Component: Build/Install
On Thu, Jan 28, 2016 at 10:05:51AM -0500, J Smith wrote:
> The standard PHP build for extensions comes with a `make test` target,
> I'll have to check on `make check`. Would `make test` itself work? I
> think some work could be done to make the tests a bit more
> PEAR-friendly, but as a start,
Are all GEOS committers ok with moving the code from SVN
to GIT, while keeping the current trac instance ?
The PHP binding is already under GIT and properly interacts
with trac, see https://trac.osgeo.org/geos/browser
Moving the core might take a bigger effort if we want
to retain references
On Fri, 5 Feb 2016, Sandro Santilli wrote:
Thanks Roger, could you provide an URL to the "rgeos"
bug tracker as a reference ? Having this rationale as a comment
on trac would also be nice. TIA
https://trac.osgeo.org/geos/ticket/767
There is no bug tracker. General practice for all