blocks|key|2212163|text|有一个tfs解决方案。Git将允许你做你想做的事情，把它塑造成你想要阅读的变化，然后在一天结束时提交给tfs。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2212164|无论如何，我还是建议改用git。|2212165|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

There is a tfs-git solution. Git will allow you to do what you want, shape it to how you want the changes to read, then commit to tfs at the end of the day.

I would recommend switching to git anyway.

blocks|key|1856743|text|TFS搁置集允许您创建类似于变更集的内容，而不是存储在主存储库中。这个搁置集是一个备份，可以由另一个开发人员从另一台机器中“提取”。这个“私有存储库”，以及“拉”它的能力，就像搁置集与DVCS相比。然而，Shelveset不是真正的存储库；它们只是快照，不维护历史记录，您不能像TFS上的源代码管理存储库那样签入或管理更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1856744|DVCS比这个多得多；有了DVCS，计算机上就有了存储库的完整副本。您可以随心所欲地在本地提交，存储您所做的每一个更改；您可以任意还原更改，因为您的计算机对所有意图和目的而言都是您的源代码管理。然后，您可以将您的更改推送到另一台计算机(中央存储库、构建机器或其他任何东西)。DVCS是一个完全不同和灵活的范例，它允许但不需要使用中央存储库。它使您不必在稳定的签入和频繁的签入之间进行选择(您可以随时随地在本地签入，在稳定时推送)。|1856745|还有更多的东西。如果您愿意，您可以查看Joel的优秀(和乡巴佬)介绍汞的DVCS在hginit.com。|offset|length|1856746|希望这能帮上忙|1856747|阿萨夫。|1856748|entityMap|0|LINK|mutability|MUTABLE|url|http://hginit.com/^0|0|0|15|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

The TFS shelveset allows you to create something akin to a changeset, that isn't stored in the main repository. This shelveset is a backup, and can be "pulled" by another developer from another machine. This "private repository", and the ability to "pull" it is as far as the shelveset compares to DVCS. Shelvesets however are not true repositories; they are merely snapshots, they do not maintain history, and you cannot check in or manage changes as you would with the source control repository on your TFS.

A DVCS is a lot more than this; with a DVCS, you have a complete copy of the repository on your machine. You can commit locally as often as you want, storing each and every change you make; you can revert changes as much as you want, since your machine is for all intents and purposes, your source control.
And then you can push your changes to another machine (central repositor, build machine, or whatever). DVCS is a completely different and flexible paradigm, that allows but doesn't require the use of a central repository. It frees you of having to choose between stable and frequent check-ins (you can check-in locally whenever you want, and push when you're stable). 

There's a lot more to it. If you like, you can checkout Joel Spolskey's excellent (and hillarious) intro to Mercurial DVCS at <a href="http://hginit.com/" rel="noreferrer">hginit.com</a>.

Hope this helps, 
Assaf.

Let's say a person is working in a small team SCRUM environment. Several teams are working on different branches of the same code base. In our team we usually split up into pairs to work on code. Occasionally people need to take time off etc. and it would be advantageous to be able to merge person A's code into person B's codebase. But they often don't want to commit at the end of the day for fear of breaking the build. 

This led me to DVCS -- well suited to P2P merging and doesn't require "the big commit". A team member suggested that TFS's shelveset would be able to do this as well. How do the two approaches compare? 

Team is currently using Subversion.

how does TFS's shelveset model compare to a DVCS?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

假设一个人在一个小型团队SCRUM环境中工作。几个团队正在同一代码库的不同分支上工作。在我们的团队中，我们通常分成两组来处理代码。偶尔，人们需要休假等，这将有利于将person A的代码合并到person B的代码库中。但是，他们通常不想在一天结束时承诺，因为害怕破坏构建。这让我想到了DVCS --非常适合P2P合并，...

问TFS的搁置集模型与DVCS相比如何？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问TFS的搁置集模型与DVCS相比如何？EN