大文件的版本控制 [英] version control on large files

查看:34
本文介绍了大文件的版本控制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们很高兴在工作中使用 SVN 作为 SCM.目前,我的二进制资产与我们的代码位于同一个 SVN 存储库中.SVN 支持非常大的文件(它流式"传输它们以保持内存使用合理),但它是 SLOOWWWWW.

We happily use SVN for SCM at work. Currently I've got our binary assets in the same SVN repository as our code. SVN supports very large files (it transmits them 'streamily' to keep memory usage sane), but it is SLOOWWWWW.

对于大约 1 GB(并且还在不断增长)的资产,您推荐什么资产管理软件?我们更喜欢分支和合并(不同的资产和配置文件分配给不同的客户).

What asset management software do you recommend, for about a GB (and growing) worth of assets? We would prefer branching and merging (different assets & config files go to different customers).

推荐答案

请注意,合并二进制文件几乎是不可能的!至少是自动的.至少我从未听说过支持二进制格式三向合并的程序.更不用说解决冲突了.

Please be very aware that it is almost impossible to merge binary files! At least automatically. At least I've never heard of a program that supports three-way merging on a binary format. Let alone conflict resolving.

这就是为什么大多数资产管理工具没有分支的原因,因为它没有意义,因为您无法再次合并.锁定和线性历史更好.如果您想分支",请复制带有历史记录的文件.

That's why most asset management tools don't have branching, since it makes little sense since you can't merge again. Locking and linear history is better. If you want to "branch", then make a copy of the file with history.

这篇关于大文件的版本控制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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