Changes between Version 20 and Version 21 of UsingGitToMaintainGDALWorkflow


Ignore:
Timestamp:
Dec 19, 2011, 8:52:26 AM (12 years ago)
Author:
Mateusz Łoskot
Comment:

Updated links to GDAL@GitHub

Legend:

Unmodified
Added
Removed
Modified

  • UsingGitToMaintainGDALWorkflow

    v20 v21  
    142142
    143143I 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 github.com/mloskot/gdal] maintained by [https://github.com/mloskot/ mloskot].
    145 I keep this Git repository updated using the svn2git utility.
     144It 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].
     145I keep this Git repository updated using the [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]: