[GRASS-dev] [GRASS-SVN] r68140 - in grass/trunk/scripts: d.correlate d.frame d.polar d.rast.edit d.rast.leg d.redraw db.dropcolumn db.in.ogr db.out.ogr db.test db.univar g.extension g.extension/testsuite g.extension.all g.manual g.search.modules g.search.modules/testsuite i.colors.enhance i.image.mosaic i.in.spotvgt i.oif i.spectral i.tasscap m.proj r.blend r.buffer.lowmem r.colors.stddev r.fillnulls r.grow r.import r.in.aster r.in.srtm r.in.wms r.mask r.out.xyz r.pack r.plane r.reclass.area r.shade r.tileset r.unpack r3.in.xyz v.build.all v.centroids v.db.addcolumn v.db.addtable v.db.dropcolumn v.db.droprow v.db.droptable v.db.join v.db.reconnect.all v.db.renamecolumn v.db.univar v.db.update v.dissolve v.import v.in.e00 v.in.geonames v.in.lines v.in.mapgen v.in.wfs v.krige v.pack v.rast.stats v.rast.stats/testsuite v.report v.unpack v.what.strds v.what.strds/testsuite wxpyimgview

Pietro peter.zamb at gmail.com
Fri Mar 25 00:54:16 PDT 2016

Hi Martin,

On Fri, Mar 25, 2016 at 8:49 AM, Martin Landa <landa.martin at gmail.com> wrote:
> I missed any discussion on ML. Such heavy changes should be discussed
> in advanced (probably I just missed it). Another question is if to
> backport such changes to relbr70. Our policy say only bugfixes. On the
> other hand, with diverse codebase the backporting will be pain. Or we
> could wait with such changes in trunk when 7.2 will be out and
> backports to 7.0 branch will not so often. So backport or revert.

Indeed there were no discussion, feel free to revert.

I'm still confused... when can I break the trunk branch? :-)


More information about the grass-dev mailing list