Re: [GRASS-dev] [GRASS GIS] #3861: winGRASS master (git) - g.proj not found at startup

2019-07-12 Thread GRASS GIS
#3861: winGRASS master (git) - g.proj not found at startup --+ Reporter: hellik | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.8.0 Component: Startup |Version: svn-trunk

Re: [GRASS-dev] Merging PRs

2019-07-12 Thread Helmut Kudrnovsky
>Any opinions on merging PRs related to MS Windows builds to .>master without testing by another person? more description why the changes and more testing before merging is welcome. it seems there is some windows dll hell issue at the moment which should be solved before the PRs can be tested.

[GRASS-dev] PROJ.6 (+ spatialite)

2019-07-12 Thread Helmut Kudrnovsky
Hi, under https://www.gaia-gis.it/fossil/libspatialite/wiki?name=PROJ.6 there is a nice overview of the new proj library functionality. maybe useful for further adopting in GRASS GIS. - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

Re: [GRASS-dev] Merging PRs

2019-07-12 Thread Markus Metz
On Fri, Jul 12, 2019 at 4:23 PM Huidae Cho wrote: > > Greetings Developers, > > In https://trac.osgeo.org/grass/wiki/HowToGit, it is not clear who is responsible for merging PRs when. Are individual core developers encouraged (allowed?) or discouraged to merge them? I'm talking about core, not

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

2019-07-12 Thread Maris Nartiss
The biggest question is – do we need PR notifications here. I would vote for no. Better let's keep discussions in one place. And no, PRs don't get lost. They all are on GitHub. If a PR was lost, that is a bug in GitHub and needs to be addressed ASAP. When we moved to the new workflow, those with

[GRASS-dev] Merging PRs

2019-07-12 Thread Huidae Cho
Greetings Developers, In https://trac.osgeo.org/grass/wiki/HowToGit, it is not clear who is responsible for merging PRs when. Are individual core developers encouraged (allowed?) or discouraged to merge them? I'm talking about core, not addons. How does it work? The main reason why I ask this

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

2019-07-12 Thread Huidae Cho
Markus, I don't think that list has PR notifications. That's only for actual merges, not everything, if I'm not wrong. Best, Huidae On Fri, Jul 12, 2019 at 9:58 AM Markus Neteler wrote: > Hi, > > On Fri, Jul 12, 2019 at 6:12 AM Huidae Cho wrote: > > > > Markus, > > > > I think I have a

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

2019-07-12 Thread Markus Neteler
Hi, On Fri, Jul 12, 2019 at 6:12 AM Huidae Cho wrote: > > Markus, > > I think I have a workaround. In the worst case scenario, if GitHub doesn't > support notification forwarding, we could create a dummy GitHub account just > for notifications and set its email address to

[GRASS-dev] Fwd: [OSGeo/grass-addons] r.in.pdal: docker support added (#16)

2019-07-12 Thread Markus Neteler
Since PRs don't arrive yet here, a manual fwd. FYI -- Forwarded message - From: AnikaBettge Date: Wed, Jul 10, 2019 at 4:27 PM Subject: [OSGeo/grass-addons] r.in.pdal: docker support added (#16) To: OSGeo/grass-addons Cc: Subscribed -- You can