颠覆和混合修订：配方破碎构建？ [英] Subversion and mixed-revisions: recipe for broken builds?

问题描述

我只是回正在添加到颠覆TFS使用一段时间后generaly我很退出:)

I'm just comming back to subversion after using TFS for some time and generaly i'm quite exited :)

有一件事我记得是不同的。我不记得beeing能够从过时的工作副本提交。或者，也许我的记忆，只不过没有我就过时的定义。我想：过时的，意味着任何文件都被感动，因为我上次更新我的工作拷贝，而不仅仅是我感动本地的文件已经被感动了（我称之为冲突）。

There is one thing i remember differently. I don't remember beeing able to commit from an out of date working copy. Or maybe my memory just fails me on the definition of "out of date". I thought "out of date" meant that any file had been touched since i last updated my working copy, and not just that a file I touched locally had been touched (what i would call a conflict).

为什么我认为这是一个问题的原因是，它使得它很容易打破建立如果我提交我的修改没有先与其他人所做的更改整合。

The reason why I see this as a problem is that it makes it very easy to "break the build" if I can commit my changes without first integrating with the changes made by others.

所以是这样的混合版本的东西添加resently或者是它只是我吗？

So was this mixed-revisions thing added resently or is it just me?

推荐答案

这是你的，因为它一直是这样的; - ）

It's you, since it has always been like this ;-)

您提交会失败，如果任何你想提交的项目是外的日期，并且存储库有一个通用的版本号，但只要一切你即将提交是向上最新的，你可以提交。这并不意味着这是当然的最佳实践。

Your commit will fail if any of the items you're trying to commit is out-of-date, and the repository has one 'general' revision number, but as long as everything you're about to commit is up-to-date, you CAN commit. That does not mean it's a best practice of course.

记住，SVN不仅在软件开发中使用。一般来说这种能力可能是不错的。

Remember that svn is not only used in software development. In general this ability is probably nice to have.

，而且，据我所知TFS作品在这方面是非常相似的，对吧？

And furthermore, AFAIK TFS works very similar in this regard, right?

这篇关于颠覆和混合修订：配方破碎构建？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！