August 2019
Beginner
608 pages
16h 7m
English
With SVN, you can set up your server to grant or deny permissions to users. You can even define finer-grained access rules based on paths. All of this is configured in a central location. With Git running on your client, there is no access control by default. Your server implementation or central repository that's running Git must do that for you. GitLab has this functionality.
The repository's change history is kept centrally on the server in the SVN world, and to change it you need to gain access to this central place.
Because Git is a distributed versioning system, every developer can make changes to any part of their local repository history. Although pushing a changed history is heavily discouraged, it is ...
Read now
Unlock full access