Using GIT for Dataflex Development: Difference between revisions
Using GIT for Dataflex Development (view source)
Revision as of 19:54, 30 September 2016
, 30 September 2016→Types of version control tools
| Line 19: | Line 19: | ||
If you are currently using a Centralised version control, you might be interested in the following list of major changes with the Distributed flavour; | If you are currently using a Centralised version control, you might be interested in the following list of major changes with the Distributed flavour; | ||
* No access to a server is required, the distributed VC has a local repository that gets synch’ed with a remote (central or peer to peer) repository when it can but can work fine on its own. | * No access to a server is required, the distributed VC has a local repository that gets synch’ed with a remote (central or peer to peer) repository when it can but can work fine on its own. | ||
* Each developer has | * Each developer has its own repository local to their working directory | ||
* No file checkout is required, just start changing the files | * No file checkout is required, just start changing the files | ||
* You can stage a number of files, so multiple files can be part of one commit (maintaining the relationship of the changes in the files) | * You can stage a number of files, so multiple files can be part of one commit (maintaining the relationship of the changes in the files) | ||