B
B
BonBon Slick2017-02-06 12:19:56
git
BonBon Slick, 2017-02-06 12:19:56

When to use SVN and when to use DVCS and GIT?

What is the best time to apply? Why?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
D
Dmitry Eremin, 2017-02-06
@BonBonSlick

SVN has a central (master) repository. Perhaps this is the key difference
Using SVN makes sense if you want to restrict access to projects within the repository.
Relatively speaking, you have 20 projects (20 folders) in your turnip. You need to give the developer access to three of them. This is easy to do in SVN (it will only see 3). In GIT, you can only grant or deny access to the entire repository.
Accordingly, if you do not have the task of allocating access to different parts of the repository, use git - it is more convenient

F
Fat Lorrie, 2017-02-06
@Free_ze

Git (or Git-like ones like Mercurial) is best used whenever there is a choice. SVNs are most often legacy projects whose change history you don't want to lose, or legacy employees who are too lazy to learn Git.
Because it has huge advantages: lightweight brunches, each user has a complete copy of the repository with a history in their hands, so you can work with a temporary lack of connection to the server.

A
Alexander Titov, 2017-02-06
@alex-t

From my own experience, I encountered a case where svn does not roll at all. There are clients who have their Internet turned off for security reasons, the only reasonable option is to go to them with a flash drive of the git repository and do synchronization.
When security "presses" even more - the repository at the client and the transfer back and forth of text packs.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question