Right, I can see why that would be useful. I was worried that using a short hashlet might not be unique [1]. But can easily do both I guess. Or maybe just a concern for future generations.
[1] https://blog.cuviper.com/2013/11/10/how-short-can-git-abbreviate/ On Thu, Feb 21, 2019 at 2:20 AM Sandro Santilli <s...@kbt.io> wrote: > On Wed, Feb 20, 2019 at 12:59:46PM -0800, g...@osgeo.org wrote: > > > - * Last port: algorithm/InteriorPointArea.java r728 (JTS-1.13+) > > + * Last port: algorithm/InteriorPointArea.java (JTS-1.17+) > > + * > https://github.com/locationtech/jts/commit/a140ca30cc51be4f65c950a30b0a8f51a6df75ba > > May I suggest to include the short commit hash on the same line as "Last > port" ? > It would help using with grep. Syntax could be something like: > > * Last port: algorithm/InteriorPointArea.java a140ca30 (JTS-1.17+) > > Having full url to the official repository is also good > > --strk; >
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
