Changes between Version 22 and Version 23 of UsingGitToMaintainGDALWorkflow


Ignore:
Timestamp:
Oct 15, 2012, 1:23:29 PM (12 years ago)
Author:
strk
Comment:

update url of git mirror

Legend:

Unmodified
Added
Removed
Modified
  • UsingGitToMaintainGDALWorkflow

    v22 v23  
    141141== GitHub Mirror ==
    142142
    143 I try to maintain up-to-date Git repository with mirror of GDAL Subversion trunk, branches and tags.
    144 It is available as [https://github.com/mloskot/gdal mloskot/gdal] or [https://github.com/mloskot/osgeo-gdal mloskot/osgeo-gdal] maintained by [https://github.com/mloskot/ mloskot].
    145 I keep this Git repository updated using the [https://github.com/mloskot/pygit-svn-mirror pygit-svn-mirror] tool (see section above).
     143There is an up-to-date Git repository with mirror of GDAL Subversion trunk, branches and tags
     144available at [https://github.com/OSGeo/gdal] maintained by Evem Roualt using
     145the [https://github.com/mloskot/pygit-svn-mirror pygit-svn-mirror] tool (see section above).
    146146
    147147Note, if you are GDAL committer, clone of this repository will not allow you to issue ''git svn dcommit'' command to push your changes back to GDAL trunk. If you expect this functionality, you need to maintain Git repository of GDAL trunk on your own according to the steps described above. Quoting one of [http://stackoverflow.com/questions/1880405/can-different-git-svn-clones-of-the-same-svn-repository-expect-to-be-able-to-shar/1880487#1880487 best practices listed here]: