blocks|key|5148303|text|wikipedia上关于修订控制的文章是一个很好的起点|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5148304|Revision+control|offset|length|5148305|在尝试教我的同事时，我发现让他在最后理解词汇表是开始向他介绍源代码控制技术的一个很好的方法。|5148306|不知道分支是什么？了解它们是如何工作的:)|5148307|在Version+Control+with+Subversion上有一本免费的在线subversion书，它提供了一个无价的参考。|5148308|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Revision_control|1|http://svnbook.red-bean.com/^0|0|0|G|0|0|0|0|1|V|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

The wikipedia article on Revision Control is a great place to start 

<a href="http://en.wikipedia.org/wiki/Revision_control" rel="nofollow noreferrer">Revision control</a>

When trying to teach my colleagues, I found getting him to understand the vocabulary at the end was a great way to start to introduce him to source code control techniques.

Don't know what a branch is? Go find out and how they work :)

There's a free online subversion book at <a href="http://svnbook.red-bean.com" rel="nofollow noreferrer">Version Control with Subversion</a> which provides an invaluable reference.

blocks|key|2893263|text|我发现这个Source+Control+HOWTO+by+Eric+sink很有用|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2893264|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ericsink.com/scm/source_control.html^0|5|X|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I found this useful <a href="http://www.ericsink.com/scm/source_control.html" rel="noreferrer">Source Control HOWTO by Eric sink</a>

blocks|key|2893538|text|我认为关于源代码控制系统，人们必须学习的最重要的要点如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893539|与源代码控制systems|2893540|forking|unordered-list-item|2893541|
相比，频繁的小型merging|2893542|rollbacks|2893543|
|2893544|conflict+resolution|2893545|2893546|exclusive分支和checkout|2893547|2893548|continuous与非排他性systems|2893549|2893550|2893551|
集成的价值|2893552|2893553|测试驱动开发和自动化单元测试|2893554|2893555|如果您已经涵盖了这些主要概念，那么对于源代码控制来说，这几乎就是您需要了解的大部分内容:)|2893556|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1C|8|@]|9|@]|A|$]]|$1|O|3|L|5|6|7|1D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|F|7|1E|8|@]|9|@]|A|$]]|$1|R|3|L|5|6|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1G|8|@]|9|@]|A|$]]|$1|U|3|L|5|6|7|1H|8|@]|9|@]|A|$]]|$1|V|3|E|5|F|7|1I|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|F|7|1K|8|@]|9|@]|A|$]]|$1|Z|3|10|5|F|7|1L|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1N|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|15|$]]

I think the most important points one has to learn regarding source control systems are the following:

<ul>
<li>the value of small, frequent check-ins/commits</li>
<li>tagging, branching and merging</li>
<li>rollbacks</li>
<li>conflict resolution</li>
<li>exclusive vs. non-exclusive checkout</li>
<li>continuous integration </li>
<li>Test-driven development &amp; automated unit tests vis-a-vis source control systems</li>
<li>forking</li>
</ul>

If you've got these major concepts covered, that's pretty much most of the things you'll ever need to know for source control :)

blocks|key|2893257|text|有几本关于这个主题的免费电子书。尝试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893258|Subversion的版本控制：Version+Control+with+Subversion|offset|length|2893259|Subversion版本控制：Subversion+Version+Control|2893260|我已经读过了，我会推荐前者。我还没有读过"Subversion版本控制“，但它看起来很深入。|2893261|entityMap|0|LINK|mutability|MUTABLE|url|http://svnbook.red-bean.com/|1|http://www.informit.com/content/images/0131855182/downloads/Nagel_book.pdf^0|0|G|V|0|0|F|Q|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

There are a couple of free ebooks on the subject. Try:

Version Control With Subversion: <a href="http://svnbook.red-bean.com" rel="nofollow noreferrer">Version Control with
Subversion</a>

Subversion Version Control (PDF): <a href="http://www.informit.com/content/images/0131855182/downloads/Nagel_book.pdf" rel="nofollow noreferrer">Subversion Version Control</a>

I have read and would recommend the former. Haven't read "Subversion Version Control", but it looks pretty in-depth.

blocks|key|5148335|text|为了回答你的问题re:我建议你在完成整个签入和签出过程后，回滚到旧版本并执行diffs，你应该看看分支。分支可以帮助您处理处于大型更改中间的痛苦，并且突然需要执行错误修复并将其部署到生产环境中，而无需在您正在处理的一半完成的工作中进行混合。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5148336|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

To answer your question re: Which are the most important points to master I would suggest that after you get through the whole checking in and out process, rolling back to old versions and performing diffs you should take a look at branching. Branching can help you deal with the pain of being in the middle of a large change and suddenly needing to perform a bug fix and deploy it to production without the mixing in the half done stuff you are working on.

blocks|key|3737388|text|我认为Subversion文档是一个很好的起点。我发现维基百科并没有真正的帮助，因为它只涵盖了一个“基本”的观点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3737389|在alex提到的中，我特别推荐第一章，尽管如果你已经有一些使用Svn的经验，第一章的水平可能会太低。第4章详细介绍了分支和合并，但这是非常技术性的。|3737390|对我帮助很大的是documentation中的TortoiseSVN日常使用指南；它以教程的形式介绍了最重要的操作。|offset|length|style|BOLD|3737391|我想你需要掌握的最重要的事情是分支，合并和标记。理解这些需要时间和实践，所以我强烈建议在本地存储库中进行一个小型的宠物项目，这样您就可以进行实验。我认为重要的是要认识到，整个系统是基于差异的:合并只不过是自动将一个分支中所做的更改应用到另一个分支中的代码，而不是自己更正代码。像冲突这样的东西(我花了相当多的时间去理解)就是这样的后果。|3737392|当然，我也还在学习:)|3737393|entityMap^0|0|0|8|D|0|F|8|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$F|V|G|W|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

I think the Subversion documentation is a good place to start. I found that Wikipedia doesn't really help, since it only covers a 'fundamental' point of view.

In the <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">Subversion Book</a> that alex mentioned, I'd especially recommend Chapter 1, although that might be on a level that's too low if you already have some experience with Svn. Chapter 4 covers branching and merging in detail, but it's quite technical.

What helped me a lot is the Daily Use Guide in the TortoiseSVN documentation; it covers the most important operations in a tutorial style.

I guess the most important things you need to grasp are branching, merging and tagging. Understanding those takes time and practice, so I'd strongly recommend a small pet project in a local repository, so you can experiment. I think it's important to realize is that the whole system is diff-based: a merge is nothing more than automatically applying the changes that have been made in one branch to the code in another branch, instead of correcting the code yourself. Stuff like conflicts (which took me quite a lot of time to understand) are just consequences of that.

But of course, I'm still learning as well :)

blocks|key|5148554|text|我也和你一样，从来没有对SVN或SourceSafe感到100%25的舒服。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5148555|查看Mercurial。Quickstart和Cheatsheets|offset|length|5148556|还有一个很棒的cheat+sheet+from+DongWoo+Lee+(他的网站似乎关闭了，所以我扫描了一下并上传到我的网站上)|5148557|使用Mercurial，一切似乎都变得更加流畅和容易，不知道为什么，因为它的命令与其他命令没有太大不同。|5148558|entityMap|0|LINK|mutability|MUTABLE|url|http://www.selenic.com/mercurial/wiki/|1|http://www.selenic.com/mercurial/wiki/index.cgi/QuickStart|2|http://www.ivy.fr/mercurial/ref/v1.0/|3|http://www.cuardo.com/pics/MercurialCheatSheet.gif^0|0|2|9|0|C|A|1|N|B|2|0|7|S|3|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]|$D|12|E|13|1|14]|$D|15|E|16|1|17]]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]|T|$5|M|N|O|A|$P|U]]|V|$5|M|N|O|A|$P|W]]]]

I also, like you, never really felt a 100% comfortable with SVN or SourceSafe. 

Check out <a href="http://www.selenic.com/mercurial/wiki/" rel="nofollow noreferrer">Mercurial</a>. <a href="http://www.selenic.com/mercurial/wiki/index.cgi/QuickStart" rel="nofollow noreferrer">Quickstart</a> and <a href="http://www.ivy.fr/mercurial/ref/v1.0/" rel="nofollow noreferrer">Cheatsheets</a> 
also a great <a href="http://www.cuardo.com/pics/MercurialCheatSheet.gif" rel="nofollow noreferrer">cheat sheet from DongWoo Lee</a> (his site seems down so I scanned it and uploaded onto mine)

With Mercurial everything seemed a lot more smooth and easy not sure why because it's not that different in commands to others.

blocks|key|2893703|text|我不确定您在版本控制系统方面有多少经验，但对于对此概念没有先验知识的人，我建议您阅读Subversion+book的前几章。这里描述的一些东西是特定于Subversion的，但许多概念对于版本控制系统以及如何使用它们是“通用的”。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2893704|我认为，在开始使用版本控制系统之前，努力理解版本控制系统背后的主要概念和原理是非常重要的。我经常看到开发人员只使用系统功能的一小部分，因为他们不理解底层概念，因此要么看不到使用他们认为“高级”或“不必要”功能的意义，要么他们只是害怕这样做，因为他们害怕破坏某些东西或给项目带来问题。|2893705|在过去与许多开发人员一起经历过这种现象后，我最近在我的博客上写了一篇关于我对best+practices+for+version+control的看法的总结。|2893706|entityMap|0|LINK|mutability|MUTABLE|url|http://svnbook.red-bean.com/|1|http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/^0|16|F|0|0|0|12|Y|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I am not sure how much experience you have with version control systems, but for someone who has no prior knowledge about the concept I recommend reading the first few chapters of the <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">Subversion book</a>. Some of the things described there are specific to Subversion, but many of the concepts are "universal" for version control systems and how to work with them. 

I think it's very important that people make an effort in trying to understand the main concepts and rationales behind version control systems before starting to use them. All too often I see developers only using a small subset of their system's features because they don't understand the underlying concepts and therefore either don't see the point in using what they consider "advanced" or "unnecessary" features, or they are simply afraid to do so in fear of breaking something or causing problems for the project.

Having experienced this phenomenon with many developers in the past, I recently wrote up a summary of what I consider <a href="http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/" rel="nofollow noreferrer">best practices for version control</a> on my blog.

blocks|key|3737679|text|请阅读：How+Software+Evolves|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3737680|entityMap|0|LINK|mutability|MUTABLE|url|http://oreilly.com/catalog/practicalperforce/chapter/ch07.pdf^0|4|K|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Read this: <a href="http://oreilly.com/catalog/practicalperforce/chapter/ch07.pdf" rel="nofollow noreferrer">How Software Evolves</a>

blocks|key|5148173|text|查看GIT。A+talk+on+it+here。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5148174|entityMap|0|LINK|mutability|MUTABLE|url|http://git.or.cz/|1|http://www.youtube.com/watch?v=4XpnKHJAok8^0|2|3|0|J|4|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Check out <a href="http://git.or.cz/" rel="nofollow noreferrer">GIT</a>. A talk on it <a href="http://www.youtube.com/watch?v=4XpnKHJAok8" rel="nofollow noreferrer">here</a>.

blocks|key|699484|text|配置管理最好的网络资源应该是Brad+Appleton的The+ACME+Project|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|699485|您应该阅读有关所有SCM模式和反模式的信息。所有的SCM技术术语都在这个网站上定义得很好，并且有很多关于分支技术，敏捷SCM和其他重要东西的文章。|699486|这可能会为您提供足够的理论背景来处理任何特定的版本工具。|699487|至于Subversion书，很可能是上面提到的官方Subversion+book。它可以在网上免费获得，也可以购买硬拷贝。|699488|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cmcrossroads.com/bradapp/acme/|1|http://svnbook.red-bean.com/^0|S|G|0|0|0|0|P|F|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

IMHO, the best network resource for Configuration Management would be <a href="http://www.cmcrossroads.com/bradapp/acme/" rel="nofollow noreferrer">The ACME Project</a> by Brad Appleton

You should read about all SCM patterns and Anti patterns.
All SCM technical terms are well defined on this site and there are many articles on branching techniques, agile SCM and other important stuff.

This, probably, will give you enough theoretical background to handle any specific version tool.

As to a Subversion book, it is probably will be the Official <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">Subversion book</a> which was mentioned above. It is available online for free or you can purchase a hard copy.

blocks|key|699531|text|我是THE+book：Berczuk的关于配置管理模式的书|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|699532|entityMap|0|LINK|mutability|MUTABLE|url|http://www.scmpatterns.com/book/^0|2|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

IMHO, this is <a href="http://www.scmpatterns.com/book/" rel="nofollow noreferrer">THE book</a>: Berczuk's book on SCM patterns

blocks|key|5148783|text|Version+control+by+example+by+Eric+Sink很好用，而且很容易理解|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5148784|entityMap|0|LINK|mutability|MUTABLE|url|http://ericsink.com/vcbe/^0|0|13|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://ericsink.com/vcbe/" rel="nofollow">Version control by example by Eric Sink</a> is good and easy to follow

Where should I start learning about version control systems? I've used SVN, Team Foundation, and Sourcesafe in the past but I don't really feel like I grasp it completely, and my team doesn't seem to grasp it either.

Which points are the most important to master? I realise this differs from VCS to VCS, but for the sake of this question we can assume that Subversion is the VCS I'm the most interested in learning about.

Also, if you could, please recommend any books on the subject that you find useful.

Learning Version Control, and learning it well

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我应该从哪里开始学习版本控制系统？我在过去使用过SVN、Team Foundation和Sourcesafe，但我真的觉得我没有完全掌握它，我的团队似乎也没有掌握它。哪些要点是最需要掌握的？我意识到这在不同的VCS中是不同的，但是对于这个问题，我们可以假设Subversion是我最感兴趣的VCS。此外，如果你可以，请推荐任何你认为有用的关于这个主题的书。

问学习版本控制，并学好它
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问学习版本控制，并学好它EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问学习版本控制，并学好它
EN