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

Paul Ramsey pramsey at cleverelephant.ca
Thu Feb 21 08:10:33 PST 2019


I’ve been putting dates YYYY-MM-DD into the headers on the ones I’ve been doing. Avoids system dependence and version numbering.
P

> On Feb 21, 2019, at 7:55 AM, Martin Davis <mtnclimb at gmail.com> wrote:
> 
> 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/ <https://blog.cuviper.com/2013/11/10/how-short-can-git-abbreviate/>
> On Thu, Feb 21, 2019 at 2:20 AM Sandro Santilli <strk at kbt.io <mailto:strk at kbt.io>> wrote:
> On Wed, Feb 20, 2019 at 12:59:46PM -0800, git at osgeo.org <mailto:git at 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 <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 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/cd7008bb/attachment.html>


More information about the geos-devel mailing list