面向 SourceSafe 用户的 Subversion
明天我必须为只使用过 VSS 的开发人员做一些迁移培训。 我已经很长时间没有以任何身份使用 VSS 了，我担心我会错过很多明显的东西。 我想要的是如果您要迁移到 VSS，您会想知道的事情的列表。 如果您负责培训某人成为 SVN 新用户，您会提到什么？
I have to do some migration training for developers tomorrow who have only ever used VSS. It's been a long time since I used VSS in any capacity and I'm concerned I'll miss a lot of obvious stuff. What I want is a list of things you would want to know if you were going to move to VSS. What would you mention if you were tasked with training someone as a new user of SVN?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
Subversion for VSS Users 是一个很好的比较，不同之处在于SVN 优于 VSS
Subversion for VSS Users is a good comparison what differs in SVN over VSS
最大的区别之一是 Subversion 使用的复制-修改-合并模型与 Visual SourceSafe 中使用的锁定-修改-解锁模型之间的差异。
Subverson 书有一个 对比较进行了相当不错的概述，并对每个方面进行了一些评价。
One of the biggest differences is that between the copy-modify-merge model used by Subversion and the lock-modify-unlock model used in Visual SourceSafe.
The Subverson book has a pretty decent overview of the comparison, with some appraisal of each.
最关键的是，许多 VSS 用户习惯于检出文件，并在编辑文件时保持锁定状态，并且通常 VSS 集成使文件保持只读状态。 显然这与 SVN 只是编辑、提交和可能合并的方法不同。
VSSer 不会熟悉诸如分支和主干之类的术语，这些功能 VSS 处理得不好。
SVN 不支持链接文件，但许多 VSS 用户可能已经习惯了这一功能。 也就是说，在 VSS 级别，多个“项目”（读取文件夹）可能包含相同的文件。 从这些项目之一中检出文件，将其从所有项目中检出，然后将其检入更新所有项目。 如果正在使用此功能，则需要找到替代方案
SVN 本身并不处理影子文件夹。 该文件夹包含项目的当前状态，就好像有人刚刚执行了“获取最新版本”一样。 执行签入时，影子文件夹也会更新。
The most critical thing is that many VSSers are used to checking out a file and whilst editing it it remains locked and usually VSS integration keeps the file read-only. Clearly this differs with the SVN just edit, commit and may be merge approach.
VSSer will not be familiar with terms such as branch and trunk, such features are handled poorly by VSS.
SVN doesn't do linked files which is a feature many VSSers may be used to. That is where at the VSS level multiple "project" (read folder) may contain the same file. Checking out the file from one of these projects checks it out from all and checking it in updates all. If this is in use an alternative needs to be found
SVN doesn't natively do shadow folders. That is a folder which contains the current state of a project as if someone had just performed a Get Latest Version. When a check-in is performed the shadow folder(s) is also updated.
上次我看到 VSS 时，它是随 VC6.0 一起提供的，所以我不知道它今天是什么样子，但对我来说，震惊的是我曾经有我的本地源副本，并且要修改任何内容，我必须先检查它。 在 SVN 中，您始终检查所有源，或者根本没有源。 我认为值得一提。
Last time I saw VSS it was shipped with VC6.0 so I don't know how it looks like today but for me shock was about that I used to have my local copy of sources and to modify anything I had to check it out first. In SVN you have all sources checked out all the time or you have no sources at all. I think it's worth to mention.