同时使用 Subversion 和 SourceSafe? [英] Using Subversion and SourceSafe at the same time?

查看:29
本文介绍了同时使用 Subversion 和 SourceSafe?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近开始了一份新工作,公司使用 Visual SourceSafe 进行源代码控制.在我之前的工作中,我们使用了 Subversion.新公司的规则"之一是,只有在您对代码工作感到满意时才提交代码,并且不会破坏构建.另一个规则是无分支"

I have recently started a new job, and the company uses Visual SourceSafe for source control. At my previous job we used Subversion. One of the 'rules' at the new company is that you only commit your code when you are happy that it works, and that it won't break builds. The other rule is 'No Branching'

这有点限制了我的风格,因为我喜欢创建一个分支,在那个分支上工作,只要我愿意就可以提交(这让我能够在我做了一些愚蠢的事情时恢复——这很常见)和然后当我很高兴一切正常时,将我的分支合并回主干.

This cramps my style a bit, as I enjoy creating a branch, working on that branch, committing whenever I wish (which gives me the benefit of being able to revert if I do something stupid -- which is quite often) and then merge my branch back into trunk when I'm happy everything works as it should.

那么,问题是...我可以将文件添加到我自己的本地 subversion 存储库中,而不会干扰 SourceSafe 吗?然后我可以随时提交到我的本地 subversion 存储库,当我对 SourceSafe 中的所有提交感到满意时?安全吗?我会破坏 SourceSafe 吗?

So, the question is... Can I add files to my own local subversion repository, and not have it interfere with SourceSafe? I can then commit to my local subversion repo whenever i wish, and when i'm happy with everything commit in SourceSafe? Is it safe? Will I break SourceSafe?

谢谢

推荐答案

您不会破坏 SourceSafe.这是在您的情况下工作的绝佳方式

You will not break SourceSafe. This is an excellent way to work in your situation

更新:忽略您不直接感兴趣的任何文件,例如 scc 文件.您的存储库不需要重新创建整个项目,只需跟踪您更改的内容即可.

Update: Ignore any file that is not of direct interest to you, such as scc files. Your repository does not need to recreate the entire project, just keep track of the things you change.

我对 Mercurial 和 CVS 做同样的事情.公司使用 CVS,我使用本地 Mercurial 存储库,我喜欢随时签入,高兴时签入 CVS.

I do the same thing with Mercurial and CVS. The company uses CVS, and I use a local Mercurial repository that I check in whenever I like, and check in to CVS when I am happy.

[旁白]

在个人层面更改源代码控制系统没问题,但对于团队来说通常会出现问题.人们习惯了源代码控制的工作方式,并利用它来发挥自己的优势.在没有完全支持的情况下更改系统,他们可能需要很长时间才能感受到优势超过了他们失去的功能.在习惯新系统的过程中,他们会犯错,失去工作,并且可能会因为您改变他们认为运行良好的系统而表示感谢.

Changing source control systems at an individual level is fine, but for a team can often be problematic. People get used to the way source controls work, and leverage that to their advantage. Change the system without total buy in and it can take a long time for them to feel the advantages outweigh the features they have lost. While getting used to the new system they make mistakes, lose work, and can be a little remiss in thanking you for changing a system they thought worked perfectly well.

这篇关于同时使用 Subversion 和 SourceSafe?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆