Possible Duplicate:
What is the difference between all the different types of version control?可能重复:所有不同类型的版本控制之间有什么区别?
Dear all:
I have just started to use SVN for version control but there always is a lot of talk going on about Version Control system like GIT, Mercurial, SVN, CVS etc.
我刚刚开始使用SVN进行版本控制,但是关于版本控制系统,如GIT,Mercurial,SVN,CVS等,总会有很多话题。
What makes one version control system better from another? Or Is one type of version control system good for one task and another type good for some other task? Or Are all the version control system basically the same?
是什么让一个版本控制系统更好?或者一种版本控制系统适用于一个任务而另一种类型适用于其他任务吗?或者所有的版本控制系统基本相同吗?
3 个解决方案
#1
No, I don't think they're the same. The centralized (e.g., SVN, CVS, etc.) versus distributed (Git, Mercurial, etc.) repository is a fundamental difference that reflects the way your development team operates.
不,我不认为他们是一样的。集中式(例如,SVN,CVS等)与分布式(Git,Mercurial等)存储库是反映开发团队运作方式的根本区别。
I use SVN. I think that my organization's collective heads would explode if a distributed SCM system like Git was introduced. It's such a different concept for most people.
我用的是SVN。如果引入像Git这样的分布式SCM系统,我认为我的组织的集体主管会爆炸。对大多数人来说,这是一个不同的概念。
#2
Distributed Version Control Systems (DVCSs) like GIT, Mercurial and Bazaar do collectively have advantages in flexibility of workflow and operation compared to centralized CVSs such as SVN or CVS. See the discussion on wikipedia.
与集中式CVS(如SVN或CVS)相比,GIT,Mercurial和Bazaar等分布式版本控制系统(DVCS)在工作流程和操作的灵活性方面共同具有优势。请参阅*上的讨论。
As for the choice among DVCSs, that's as highly debated as (say) that between vi and emacs;-). On a "horses for courses" basis you might pragmatically pick hg (Mercurial) if you're going to be using code.google.com, Bazaar if you're going to use Launchpad, GIT if you're going to use github, for example.
至于DVCS之间的选择,这与(比如说)vi和emacs之间的争论很多;-)。在“马匹课程”的基础上,你可以实际选择hg(Mercurial),如果你打算使用code.google.com,Bazaar,如果你要使用Launchpad,GIT,如果你打算使用github,例如。
#3
Most of it is personal preference; Git and Mercurial are distributed source control systems, and better if you have a distributed team; for the majority of development environments where the team is in the same location or connected to a single server, then the regular version control systems like Subversion are good enough.
大多数是个人偏好; Git和Mercurial是分布式源代码控制系统,如果你有一个分布式团队,那就更好了;对于团队位于同一位置或连接到单个服务器的大多数开发环境,Subversion等常规版本控制系统就足够了。
I've used Git and like it, but I actually like Subversion better. If you're using SVN you should be fine.
我已经使用过Git并且喜欢它,但我实际上更喜欢Subversion。如果你正在使用SVN,你应该没问题。
#1
No, I don't think they're the same. The centralized (e.g., SVN, CVS, etc.) versus distributed (Git, Mercurial, etc.) repository is a fundamental difference that reflects the way your development team operates.
不,我不认为他们是一样的。集中式(例如,SVN,CVS等)与分布式(Git,Mercurial等)存储库是反映开发团队运作方式的根本区别。
I use SVN. I think that my organization's collective heads would explode if a distributed SCM system like Git was introduced. It's such a different concept for most people.
我用的是SVN。如果引入像Git这样的分布式SCM系统,我认为我的组织的集体主管会爆炸。对大多数人来说,这是一个不同的概念。
#2
Distributed Version Control Systems (DVCSs) like GIT, Mercurial and Bazaar do collectively have advantages in flexibility of workflow and operation compared to centralized CVSs such as SVN or CVS. See the discussion on wikipedia.
与集中式CVS(如SVN或CVS)相比,GIT,Mercurial和Bazaar等分布式版本控制系统(DVCS)在工作流程和操作的灵活性方面共同具有优势。请参阅*上的讨论。
As for the choice among DVCSs, that's as highly debated as (say) that between vi and emacs;-). On a "horses for courses" basis you might pragmatically pick hg (Mercurial) if you're going to be using code.google.com, Bazaar if you're going to use Launchpad, GIT if you're going to use github, for example.
至于DVCS之间的选择,这与(比如说)vi和emacs之间的争论很多;-)。在“马匹课程”的基础上,你可以实际选择hg(Mercurial),如果你打算使用code.google.com,Bazaar,如果你要使用Launchpad,GIT,如果你打算使用github,例如。
#3
Most of it is personal preference; Git and Mercurial are distributed source control systems, and better if you have a distributed team; for the majority of development environments where the team is in the same location or connected to a single server, then the regular version control systems like Subversion are good enough.
大多数是个人偏好; Git和Mercurial是分布式源代码控制系统,如果你有一个分布式团队,那就更好了;对于团队位于同一位置或连接到单个服务器的大多数开发环境,Subversion等常规版本控制系统就足够了。
I've used Git and like it, but I actually like Subversion better. If you're using SVN you should be fine.
我已经使用过Git并且喜欢它,但我实际上更喜欢Subversion。如果你正在使用SVN,你应该没问题。