Speed is another important factor, and the differences between Git and other DVCS here are evident. Git saves quite some time in your daily workflow. You can work without constraints, even if you’re not connected to the network. Being able to work offline is an important advantage of DVCS for many developers. A DVCS can be used independently of any one person’s workflow. It doesn’t matter whether you’re using a complex set-up with multiple remote repositories or you have just one central server to share code (working “Subversion style”). One of Git’s main advantages is its distributed nature. However, this is not a requirement every developer can perform all important actions in their local repository: committing changes, viewing differences between revisions, switching branches, etc. In most set-ups there’s an additional central repository on a server that’s used for sharing. In distributed systems, each developer has their own full-fledged repository on their computer. And because it usually resides on a central server, each action has to pass through the network - leaving a developer unable to work if they happen to have no network connection. Every action must be synchronized with this central repository. In centralized systems, there is only one “master” repository, which every developer feeds their changes into. The classic systems like Subversion and CVS, in contrast, function as centralized systems (CVCS). Git (like Mercurial) is a “distributed” version control system (DVCS). The large number of tutorials and tools, including desktop clients, shows how important Git has become. Git is now used in countless well-known open-source projects: the Linux kernel, jQuery, Ruby on Rails, Symfony, CakePHP, Debian, Fedora, Perl and many more. Both have their origins in this emergency, and they are among today’s leading distributed version control systems. The Linux community took action by starting two new projects: Git and Mercurial. An alternative had to be found, one that was distributed, scalable and - above all - fast. Once the proprietary version control system BitKeeper changed its license agreement, it couldn’t be used to manage the Linux kernel project anymore. Linus Torvalds was unsatisfied: none of the version control systems (VCS) available in 2005 met his requirements.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |