具有历史记录的存储库之间的SVN复制 [英] SVN copy between repositories with history

查看:121
本文介绍了具有历史记录的存储库之间的SVN复制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的一个队友问是否可以在保持历史记录的同时从一个SVN导出到另一个。

One of my teammates has asked if it is possible to export from one SVN to another, all while maintaining history.

对我来说,这似乎是

因此:是否可以在所有SVN存储库之间迁移同时保持历史记录?

重要的是要注意,我们在Source上没有svnadmin访问权限,但在Destination上却具有svnadmin访问权限。

It is important to note that we do not have svnadmin access on the Source, but we do have that on the Destination.

如果出现这种情况只需从源中签出每个修订,然后将其签入到目的地,只要有一个自动化的过程,我们就可以了。

If this comes down to just checking out each revision from the source, and checking it in to the destination, we would be OK with that, as long as there was an automated process for that.

编辑:我忘了提到目标存储库在Windows上。

I forgot to mention that the destination repo is on windows.

推荐答案

[编辑:以下原始回复来自SVN 1.7之前的版本,这是解决问题的最佳方法(尽管它不是 svnsync )。在SVN 1.7客户端或更高版本中,存在 svnrdump 工具,它可以更直接地完成您要实现的目标)]

[Edit: The original reply below is from pre SVN 1.7, and there this was the best way to solve the problem (although it is not the primary use case of svnsync). In SVN 1.7 client or later there is the svnrdump tool that does more directly what you are trying to achieve)]

使用 svnsync 可以将源同步到目标(需要管理员访问目标存储库或至少一种添加挂钩的方法,但对源存储库没有特殊访问权限。如果目标已经有修订,请将源同步到临时存储库,然后使用 svn-merge-repos.pl 合并两个本地存储库。

use svnsync to synchronize the source to the destination (needs admin access to the destination repository or at least a way to add hooks, but no special access to the source repository). If the destination already has revisions, sync the source to a temporary repository, and then use svn-merge-repos.pl to merge the two local repositories.

这篇关于具有历史记录的存储库之间的SVN复制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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