TL;DR：我正在寻找一个 DVCS，其命令集比 Git 更简单（且危险性更小），它在 Windows 和 MacOS X 上运行良好。
给你一些背景知识：
我一直在 寻找我公司唯一一个测试 Git 版本控制大约 6 个月的人。
今天我意识到，当我不得不花费一天的大部分时间来恢复损坏的存储库时，Git 对于我的同事来说实际上太重了。
我是一名 .NET 和 Rails 开发人员，我非常喜欢 UNIX！
我学院的其他人都是数据专家和 Excel 开发人员（随心所欲地取笑，但他们用 Excel VBA 和 T-SQL 中的数据做一些严肃的核心工作）。
另一方面，他们无法忍受 unix，并且对使用命令行做任何事情（除了怀旧）的想法感到厌恶。
虽然我知道现在有一些很棒的 Git GUI，并且 CLI 已经有了一些巨大的改进，但 Git 对他们来说在工作流程上仍然存在巨大差异，因为他们当前使用 dropbox 来协作处理工作表代码等。
目前唯一的选择似乎是是善变的。
这是否足够接近我们需要的东西，或者是否有更简单的东西（一个很棒的 GUI 也很好）？
顺便说一句：开源不是必需的，我们愿意花一些钱。
经过深思熟虑，我决定暂时放下这件事。我自己真的很喜欢 Git，但有些人就是无法接受修订控制。
因此，我将继续在 Web 团队中强制使用 Git，但不要打扰数据迷！
TL;DR: I'm looking for a DVCS with a much simpler (and less dangerous) command set than Git, which rocks on Windows and MacOS X.
To give you some background:
I've been the only one testing Git for Revision Control at my company for about 6 months.
I realized today that Git is actually WAY too heavy for my colleagues when I had to spent a good chunk of the day restoring a corrupted repository.
I'm a .NET and Rails developer and I really like UNIX!
The rest of my colleges are data bods and Excel developers (make fun all you like but they do some SERIOUSLY hard-core stuff with data in Excel VBA and T-SQL).
On the other hand, they can't stand unix and barf at the idea of using the command line for anything except nostalgia.
While I know there are some great Git GUIs now and the CLI has seen some massive improvements, Git is still a massive difference in workflow for them as they use currently dropbox to collaborate on worksheet code etc..
At the moment the only option seems to be Mercurial.
Is this close enough to what we need or is there something simpler (a great GUI would be nice too)?
By the way: Open Source isn't necessary and we're open to spending some money.
After much thinking I've decided to leave things for now. I really enjoy Git myself but some people just can't get on board with revision control.
So I'll continue to force Git on the web team but leave the data nerds be!
发布评论
评论（6）
Mercurial 是一种简单的 DVCS，也是一种功能强大的扩展型 DVCS。
Subversion 较旧，拥有更多 UI 工具，但 DVCS 也不甘落后。
您可以使用可在 Windows 上使用的 UI：TortoiseHg，并且有 http://jasonfharris.com/machg/ 这是 Mac 的震撼 UI。
Mercurial is simple DVCS and a powerful one to extend.
Subversion being older has more UI tools but DVCS are not far behind.
You could use a UI : TortoiseHg which can be used on windows and there is http://jasonfharris.com/machg/ which is rocking UI for Mac.
不要放弃 git。培训和支持，他们会喜欢的。我在同一条船上，我们最终取得了领先。非常值得付出努力。
如果 Gitk 和 git gui 不适合命令行，那么它们就很棒。
您正在走上一条不使用 Photoshop 的图形工作室之路，因为它“太难学” - 所以他们选择了 MS Paint。不要那样做。
更新：
通过使用 git 属性，您可以将 excel 文件存储为未压缩的 xml。您现在可以在它们之间进行差异。不确定这会有多大用处。这取决于您要更改的 Excel 工作表的数量和方式。
希望这有帮助。
Don't give up on git. Train and support and they will like it. I was in the same boat and we came out ahead in the end. Well worth the effort.
Gitk and git gui are great if they are command line adverse.
You are heading down a path of a graphic studio not using Photoshop because it's "too hard to learn" - so they go with MS Paint. Don't do that.
UPDATE:
With the use of git attributes, you can store the excel files as uncompressed xml. You can now do diffs between them. Not sure how useful that would be. It depends of how much of the excel sheets you are changing and how.
Hope this helps.
回购协议可能会在任何 VCS 中损坏。与 git 的有趣区别在于，错误通常更容易恢复，而不仅仅是从备份中进行简单恢复，尽管您已经发现它可能需要一些真正的巫术。不过，这并不排除从备份选项中进行更轻量的恢复。
就我个人而言，我认为bazaar是最适合初学者自学的DVCS。他们有很棒的文档和对新手友好的社区。这就是我开始做的事情。然而，即使你拥有足够多的 git 经验，我想你也会发现集市的限制。 Mercurial 在功能和功能上与 git 更接近，并且命令行不那么unixy，但无论如何你都会避免使用CLI。
我建议将它们放在 TortoiseGit 上。无论如何，工作流程对他们来说都将是一个改变，你可以采取一些措施来让他们变得更轻松。请记住，他们将从您那里获得培训和支持，这比 git 手册页或您一直在使用的任何内容对他们来说更加适合新手。
我建议在不进行任何分支的情况下启动它们，只需从 master 拉取、提交并推送到 origin 即可。使用 TortoiseGit 与任何其他 VCS 一样简单。如果他们需要同时处理多个分支，请使用不同的存储库创建一个不同的本地文件夹，这与您所能获得的最接近的保管箱共享差不多。然后，当他们开始需要时，您可以引入更高级的概念。
Repos can corrupt in any VCS. The interesting difference with git is that the errors are more often recoverable beyond just a simple restore from a backup, although as you've discovered it can take some real voodoo. That doesn't preclude the lighter restore from backup option, though.
Personally, I think bazaar is the easiest DVCS for a beginner to learn on their own. They have great documentation and a newbie-friendly community. It's what I started out on. However, with as much git experience as you have, I think you would find bazaar limiting. Mercurial is much more on par with git feature and power-wise, and has a less unixy command line, but you're going to be avoiding the CLI anyway.
I would recommend putting them on TortoiseGit. The workflow is going to be a change for them no matter what, and there are things you can do to make it easier for them. Remember they will be getting training and support from you, which is going to be much more newbie-friendly to them than the git man pages or whatever you've been using.
I would recommend starting them out without any branching, just pull, commit, and push from master to origin. This is just about as easy with TortoiseGit as with any other VCS. Create a different local folder with a different repository if they need to work on more than one branch at once, which is about as close to dropbox sharing as you can get. Then you can introduce more advanced concepts as they start to demand them.
Mercurial/TortoiseHg 和 Bazaar/TortoiseBzr是我能想到的DVCS除了 Git 之外，那是开源的。
Mercurial/TortoiseHg and Bazaar/TortoiseBzr are the DVCS I could think of other than Git thats opensource.
您可以查看http://www.infoq.com/articles/dvcs-guide其中记录了 3 种最流行的 DVCS 之间的差异。它有关于易用性的部分，可以让您将其与功能进行比较。
You might look at http://www.infoq.com/articles/dvcs-guide which documents the differences between the 3 most popular DVCSes. It has sections on ease-of-use and lets you compare that against features.
正如您提到的，他们使用的主要格式是 Excel 电子表格，与当前的 Dropbox 解决方案相比，DVCS 的使用似乎并不像听起来那么明显。
大多数 (D)VCS 都将 Excel 电子表格视为二进制文件，甚至是 .XLSX 格式（基本上是一组压缩的 XML 文件）。因此，VCS 无法真正进行版本之间的比较，更无法执行合并。知道这一点后，Dropbox 并没有那么糟糕，因为它允许他们自动从最后 30 天的修订备份中受益，甚至还有所谓的“pack-rat”解决方案来回溯到更早的时间。
因此，考虑到这一点，我宁愿不推荐 DVCS，因为如果不仔细遵循工作流程，它可能会增加合并问题，并倾向于使用 SVN 之类的东西，它有一个“锁定”命令来防止其他用户提交错误地处理此类文件。
对于 GUI 部分，我推荐 Mac 版 版本 和 Vercue for Windows（或者当然，总是有 TortoiseSVN 选项）。
As you mention that the main kind of format they use are excel spreadsheet, the usage of a DVCS compare to their current dropbox solution seems less obvious than it might sound.
Excel spreadsheet are considered by most of the (D)VCS as binary files, even the .XLSX format (which is basically a set of XML files zipped). So the VCS won't really be able to do a comparison between versions and even less to perform a merge. Knowing that, Dropbox is not that bad as it allows them to benefit automatically from a backup of the 30 last days of revision, and even a so called "pack-rat" solution to go more back in time.
So, with that in mind, I would rather not recommend a DVCS as it could increase the merge problem if the workflow is not carefully followed and go in favor of something like SVN, which has a "lock" command to prevent other users to commit erroneously on such files.
For the GUI part, I would recommend Version for the Mac and Vercue for Windows (or course, there is always the TortoiseSVN option).