On Thu, May 31, 2018 at 12:27 AM, <svn_grass@osgeo.org> wrote:
Author: lucadelu
Date: 2018-05-30 15:27:40 -0700 (Wed, 30 May 2018)
New Revision: 72750
Modified:
grass/trunk/lib/python/pygrass/vector/__init__.py
grass/trunk/lib/python/pygrass/vector/find.py
grass/trunk/lib/python/pygrass/vector/geometry.py
Log:
working on #2881, should it backport?
Maybe commit msg are not ideal for opening discussion 
If it fixes a bug, yes, otherwise probably not.
Best, Markus
On Thu, May 31, 2018 at 4:35 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Thu, May 31, 2018 at 12:27 AM, <svn_grass@osgeo.org> wrote:
Author: lucadelu
Date: 2018-05-30 15:27:40 -0700 (Wed, 30 May 2018)
New Revision: 72750
Modified:
grass/trunk/lib/python/pygrass/vector/init.py
grass/trunk/lib/python/pygrass/vector/find.py
grass/trunk/lib/python/pygrass/vector/geometry.py
Log:
working on #2881, should it backport?
Maybe commit msg are not ideal for opening discussion 
Right, we even have guidelines for that (added modified version of this as an example, I hope that’s OK 
https://trac.osgeo.org/grass/wiki/Submitting/General#Commitmessages
If it fixes a bug, yes, otherwise probably not.
Looking at the code, looks like a very clear fix of a bug, so yes for backport.