Git存储库向后兼容 [英] Git repository backwards compatibility

查看:116
本文介绍了Git存储库向后兼容的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚才有一个关于git的快速问题 - git存储库如何向后兼容?例如,我已经使用git 1.6.4和svn2git ruby​​脚本创建了一个存储库,但我想将它放在运行Debian Lenny的机器上,该机器上安装了git 1.5.6.5。我仍然能够正确地与存储库进行交互吗?

I just had a quick question about git - how backwards compatible are git repositories? Eg., I've created a repository using git 1.6.4 and the svn2git ruby script, but I want to put it on a machine that's running Debian Lenny, which has git 1.5.6.5. Would I still be able to interact with the repository properly?

推荐答案

它在信息的实际存储方面极其向后兼容,这是你在这种情况下所担心的。我不是一个完全的专家,但我怀疑这是自第一次稳定版本以来改变了。

It's extremely backward compatible in terms of the actual storage of information, which is all you're worried about in this case. I'm not a total expert, but I doubt that's changed since the first stable release.

我认为唯一的兼容性问题是如果两个版本的git正在处理完全相同的repo(而不是克隆),并且在.git / config中设置的选项/别名可以在新版本中使用,但在旧版本中没有[完全]实现......但即便如此,我们必须努力尝试这个版本。再次,这与回购中的实际信息无关,只是用于管理它的命令。这就是git开发的地方。

The only compatibility problem I can think come up with is if the two versions of git are working on the exact same repo (not clones) and there are options/aliases set in the .git/config that work in the newer version but were not [fully] implemented in the older version... but even then you'd have to try pretty hard with versions this close. And again, this isn't anything to do with the actual information in the repo, just the commands you use to manage it. That's where the development of git is taking place.

这篇关于Git存储库向后兼容的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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