> In this case, I will follow GitHub recommendation [1] to update a PR > with separate/new commits, but not push-forcing. > For example, I'm about to update .travis.yml with libjxr-dev installation in > some of gdal/ci/travis/.../before_install.sh scripts, which I'm going to > push as a new commit. > > Any objections to this approach?
That's fine. Anyway, at some point, when this will go back to SVN, git PR history will be lost Even -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
