[geos-devel] [geos-commits] [SCM] GEOS branch master updated. edc36747409058cb10aeb8d9505d280dfbfcf697

[Martin Davis]

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 <strk at 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 at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20190221/a25896a9/attachment.html>