On Sat, 6 Jun 2020 at 14:53, Regina Obe wrote:
>
> Jaime,
>
> Sorry it took so long for you to get a mantra. I think we are usually more
> responsive but I've personally been very busy the past few weeks.
> Seems Covid only added more work for me.
>
thanks for the help! i understand that!
> If
Jaime,
Sorry it took so long for you to get a mantra. I think we are usually more
responsive but I've personally been very busy the past few weeks.
Seems Covid only added more work for me.
That said -- we are pretty open to getting pull requests from any of our code
mirrors outlined below
h
On Sat, 6 Jun 2020 at 11:34, Darafei "Komяpa" Praliaskouski
wrote:
>
> Hello,
>
> You followed the best practice to report it. Trac is officially a bug tracker.
>
> Best way to get it fixed is to stomp it into a Github pull request with
> minimized version of your case in regress suite.
> Somewhe
Hello,
You followed the best practice to report it. Trac is officially a bug
tracker.
Best way to get it fixed is to stomp it into a Github pull request with
minimized version of your case in regress suite.
Somewhere in here:
https://github.com/postgis/postgis/tree/master/raster/test/regress - pr
Hi,
I reported a bug in postgis-devel[1] two days ago, and the day after
that asked for a mantra for an osgeo id to report it in trac.
None has received answers. So i wonder where is the best place to
report these issues?
i have another bug to report.
[1] https://lists.osgeo.org/pipermail/postgi
