blocks|key|1275326|text|要做到这一点，最好的方法是使用git+svn作为Subversion客户端。这提供了Subversion存储库和Git存储库之间的双向集成。一旦有了Git存储库，您就可以将其推送到其他任何地方来发布它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1275327|我经常这样做，在工作中有一个Subversion存储库，它是“主”存储库，我通常使用git+svn来访问它。有时，如果我做的事情需要更具体的Subversion功能，比如合并，我会使用常规的svn客户端来代替存储库。|1275328|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-svn^0|F|7|F|7|0|0|16|7|2N|3|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

The best way to do this is to use <a href="http://git-scm.com/docs/git-svn" rel="noreferrer"><code>git svn</code></a> as a Subversion client. This provides two-way integration between a Subversion repository and a Git repository. Once you have a Git repository, you can push that anywhere else to publish it.

I do this regularly, at work there is a Subversion repository that is the "master" repository, and I usually use <code>git svn</code> to access it. Sometimes if I'm doing things that need more specific Subversion functionality like merging, I'll use the regular <code>svn</code> client against the repository instead.

blocks|key|4038506|text|有一个新的解决方案可以完全执行您想要的功能-+SubGit。它是并发安全的(我不能说基于git-svn的bash脚本是并发安全的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4038507|entityMap|0|LINK|mutability|MUTABLE|url|http://subgit.com/^0|N|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There's a new solution that performs exactly what you want --- <a href="http://subgit.com" rel="noreferrer">SubGit</a>. It is concurrent-safe (I can't say the same about git-svn-based bash scripts).

blocks|key|4883679|text|我们的团队遇到了完全相同的问题，经过一些实验，我们设法想出了一个git-Subversion桥，它可以在我们的团队git存储库和企业Subversion存储库之间同步更改。我们的git使用对其他Subversion用户是透明的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4883680|在https://github.com/mrts/git-svn-bridge上对设置进行了更详细的描述。|offset|length|4883681|我们在生产中使用这个设置已经有一年多了。|4883682|我想设置中最大的警告是git仓库只跟踪SVN主干(或另一个单一分支)，因此在合并到主干期间，其他git分支将被压缩到一个提交中。对我们来说，这不是问题--我们使用短暂的任务分支，并认为它们是轻量级的、短暂的“工作单元”，可以在单个块中转到主线上-分支历史记录保留在git中。|4883683|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mrts/git-svn-bridge^0|0|1|12|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Our team had exactly the same problem and after a bit of experimentation we managed to come up with a git-Subversion bridge that synchronizes changes between our team git repository and the corporate Subversion repository. Our git usage is transparent to other Subversion users.

The setup is described in more detail at <a href="https://github.com/mrts/git-svn-bridge" rel="noreferrer">https://github.com/mrts/git-svn-bridge</a>.

We have used this setup in production for more than a year.

I guess the biggest caveat of the setup is that the git repository tracks only SVN trunk (or another single branch), thus other git branches will be squashed into one commit during merge to trunk. For us this is no problem - we use short-lived task branches and consider them to be lightweight, ephemeral "units of work" that can go to mainline in a single chunk - and the branch history is retained in git.

blocks|key|4883471|text|您可能会考虑使用轻松地将svn导入git，然后再导入它的镜像ruby应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4883472|更多详细信息，请访问this+question。|offset|length|4883473|正如在其他答案中提到的，'git+svn‘是强制性的，但这些ruby模块帮助你尊重"subversion分支/目录“，而不是将它们作为实际的目录。|style|CODE|4883474|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/572893/cloning-a-non-standard-svn-repository-with-git-svn/572898#572898^0|0|A|D|0|0|D|7|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@$D|X|E|Y|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

You might consider <a href="http://github.com/iteman/svn2git/tree/master" rel="nofollow noreferrer">svn2git</a> to easily import svn to git, and then its mirror ruby application <a href="http://repo.or.cz/w/git2svn.git" rel="nofollow noreferrer">git2svn</a>. 
More details in <a href="https://stackoverflow.com/questions/572893/cloning-a-non-standard-svn-repository-with-git-svn/572898#572898">this question</a>. 
As mentioned in the other answers, '<code>git svn</code>' is mandatory, but those ruby modules help you respect the "subversion branches/directory" while not having them as an actual directory in Git.

blocks|key|820213|text|您可能还想看看这个解决方案：http://unethicalblogger.com/posts/2008/10/git_back_subversion_mostly_automagically_part_33，它用于在git和subversion之间同步存储库，多个开发人员同时使用git和subversion，并在它们之间使用一个代理来进行同步。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|820214|entityMap|0|LINK|mutability|MUTABLE|url|http://unethicalblogger.com/posts/2008/10/git_back_subversion_mostly_automagically_part_33^0|E|2I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might also want to check out this solution: <a href="http://unethicalblogger.com/posts/2008/10/git_back_subversion_mostly_automagically_part_33" rel="nofollow noreferrer">http://unethicalblogger.com/posts/2008/10/git_back_subversion_mostly_automagically_part_33</a> , which was used to synchronize a repo between git and subversion, with multiple developers using both git and subversion, and a proxy between them to do the synchronization.

blocks|key|4038464|text|我有一个bare-git+central+repos+%2B+SVN-git+bridge+-a+repos+with+git+svn，在分支'current‘中跟踪SVN，在分支'gitcentral’中跟踪GIT存储库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4038465|然后，我在中央git代码库中使用post-update+hook，如下所示：|4038466|#!/bin/bash

#+Anything+inserted+into+GIT+-+move+it+back+to+SVN

echo
echo+'*+Pushing+data+into+SVN+branch'
cd+/home/git/BRIDGE
unset+GIT_DIR

#+current+-+svn+branch+locally+and+central+git+branch+on+project.git+repos
#+centralgit+-+unmodified+centralgit+branch
git+fetch+/home/git/repositories/project.git/+master:centralgit+%7C%7C+(echo+"Error+while+pulling+data+into+bridge+repository";+exit+1)
git+checkout+-b+temp+centralgit+%7C%7C+exit+2
git+rebase+current+%7C%7C+exit+3
git+checkout+current+%7C%7C+exit+4
git+reset+--hard+temp+%7C%7C+exit+5
git+svn+dcommit+%7C%7C+exit+6
git+branch+-D+temp+%7C%7C+exit+7

echo+'*+Pushed+correctly+data+into+SVN'
exit+0|code-block|syntax|javascript|4038467|这主要是时间上的，但很有效...|4038468|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I have a bare-git central repos + SVN-git bridge - a repos with git svn, tracking SVN in branch 'current' and tracking GIT repository in branch 'gitcentral'

Then I use post-update hook in central git repos like that:

<pre><code>#!/bin/bash

# Anything inserted into GIT - move it back to SVN

echo
echo '* Pushing data into SVN branch'
cd /home/git/BRIDGE
unset GIT_DIR

# current - svn branch locally and central git branch on project.git repos
# centralgit - unmodified centralgit branch
git fetch /home/git/repositories/project.git/ master:centralgit || (echo "Error while pulling data into bridge repository"; exit 1)
git checkout -b temp centralgit || exit 2
git rebase current || exit 3
git checkout current || exit 4
git reset --hard temp || exit 5
git svn dcommit || exit 6
git branch -D temp || exit 7

echo '* Pushed correctly data into SVN'
exit 0
</code></pre>

That's mostly temporal, but works...

blocks|key|4038323|text|当然，更简单的方法是将主存储库保留为Subversion，但在本地使用git-svn？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4038324|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Surely an easier way to do it would be to have the main repository stay as Subversion, but use git-svn locally?

I want to access a repository using both GIT and SVN clients. A way I imagined to do that is through automatic two-way migration: when a user PUSHes into the GIT repository, it is also COMMITed in the SVN repository and vice-versa.

There is any tool that would help me to do that?

There is any way to synchronize GIT and Subversion repositories?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我想同时使用GIT和SVN客户端访问存储库。我设想的一种方法是通过自动双向迁移:当用户通过PUSHes进入GIT存储库时，它在SVN存储库中也是COMMITed，反之亦然。有什么工具可以帮我做到这一点吗？

问有什么方法可以同步GIT和Subversion存储库吗？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有什么方法可以同步GIT和Subversion存储库吗？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有什么方法可以同步GIT和Subversion存储库吗？
EN