[GRASS-dev] [GRASS GIS] #2876: r.sun (mode 1): data are not timestamped correctly
Thomas Huld
thomas.huld at gmail.com
Tue Apr 5 11:55:57 PDT 2016
I presume that by "backport" you mean port of this fix to GRASS7?
On 28 February I reported bug #2941 with a suggested patch to Grass 7 to
cover this. Since I'm not a regular contributor, I don't really know what
has happened to it?
It's just a one-liner, so maybe it would be safest if one of the regulars
would apply the patch?
Thomas
On Tue, Apr 5, 2016 at 11:17 AM, GRASS GIS <trac at osgeo.org> wrote:
> #2876: r.sun (mode 1): data are not timestamped correctly
> -----------------------------+-------------------------
> Reporter: fabriziosossan | Owner: grass-dev@…
> Type: defect | Status: new
> Priority: normal | Milestone: 7.0.4
> Component: Raster | Version: 6.4.5
> Resolution: | Keywords: r.sun
> CPU: x86-64 | Platform: Linux
> -----------------------------+-------------------------
>
> Comment (by martinl):
>
> Is there any plan for backport? It's noted in
> wiki:Grass7Planning#a7.0.4tobebackported and we are close to RC1 (15/4)...
>
> --
> Ticket URL: <https://trac.osgeo.org/grass/ticket/2876#comment:5>
> GRASS GIS <https://grass.osgeo.org>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20160405/6ed039e5/attachment.html>
More information about the grass-dev
mailing list