Is the JTS commit URL even useful then? Paul says he puts it into the GEOS commit msg, which seems potentially useful. Although there may be multiple commits to get a port completed (ahem - mea culpa). But there's probably a big initial commit which will be obvious.
I'm tempted to say let's do it all - but might be tedious: Last port: algorithm/InteriorPointArea.java (JTS-1.17 - 2019/02/19 - a140ca30cc5 ) On Thu, Feb 21, 2019 at 10:44 AM Sandro Santilli <s...@kbt.io> wrote: > On Thu, Feb 21, 2019 at 10:32:48AM -0800, Martin Davis wrote: > > So we understand, what is the use case here? Are you grepping to find > all > > GEOS files which were changed from a given JTS commit? > > > > If so, do you want any extra tag for the hashlet? Give us an example of > > the standard form... > > Use case is: to get a feel of which files were ported when, I grep > for 'Last Port' in all files. > > Works better with SVN revisions and dates and human readable versions > than with hashes indeed, so feel free to leave the hash where it is :) > > --strk; > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
