我一直在用Git做我所有的工作,并将其推送到GitHub。我对软件和网站都很满意,我不希望在这一点上改变我的工作实践。

我的博士导师要求所有学生将作业保存在学校托管的SVN存储库中。我发现了大量关于将现有的SVN存储库下拉到Git中的文档和教程,但没有关于将Git存储库推到新的SVN存储库中的文档和教程。我希望通过结合Git -svn、一个新的分支和rebase以及所有这些美妙的术语来实现这一点,但我是Git新手,对其中任何一个都没有信心。

然后,当我选择时,我希望只运行几个命令将提交推到SVN存储库。我希望继续使用Git,让SVN存储库镜像Git中的内容。

我将是唯一一个致力于SVN的人,如果这有什么不同的话。


当前回答

有三种方法:

Rebase:与其他答案相同 提交id:查找SVN的第一个提交id和git的第一个提交id,将它们回显到。git/info/grafts:echo "git_id svn_id}" > .git/info/grafts then git SVN dcommit 检查每一个git提交,复制文件到svn_repo, SVN提交

bash演示: github演示

v1。X:使用rebase和commit id

v2。X:使用复制文件,然后SVN提交

其他回答

还有一个有效的序列(每个步骤都有一些注释):

Install git-svn and subversion toolkits: sudo apt-get install git-svn subversion Switch inside the PROJECT_FOLDER cd PROJECT_FOLDER Create the project path on the Subversion server (unfortunately the current git-svn plugin has a defect in comparison with TortoiseSVN). It is unable to store source code directly into the PROJECT_FOLDER. Instead, by default, it will upload all the code into PROJECT_FOLDER/trunk. svn mkdir --parents protocol:///path/to/repo/PROJECT_FOLDER/trunk -m "creating git repo placeholder"

在这里,中继在路径的末端是强制性的

Initialize the git-svn plugin context inside the .git folder git svn init -s protocol:///path/to/repo/PROJECT_FOLDER This is the place where trunk at the end of the path is unnecessary Fetch an empty Subversion repository information git svn fetch This step is helping to synchronize the Subversion server with the git-svn plugin. This is the moment when git-svn plugin establishes remotes/origin path and associates it with the trunk subfolder on the server side. Rebase old Git commits happened before the git-svn plugin became involved in the process (this step is optional) git rebase origin/trunk Add new/modified files to commit (this step is regular for Git activities and is optional) git add . Commit freshly added files into the local Git repository (this step is optional and is only applicable if step 7 has been used): git commit -m "Importing Git repository" Pushing all the project changes history into the Subversion server: git svn dcommit

如果您希望继续使用Git作为您的主存储库,并且只需要不时地将修订“导出”到SVN,那么您可以使用Tailor来保持SVN存储库的同步。它可以在不同的源代码控制系统之间复制修订,并将您在Git中所做的更改更新到SVN。

我没有尝试过git到SVN的转换,但是对于一个SVN -> SVN示例,请参阅这个答案。

有三种方法:

Rebase:与其他答案相同 提交id:查找SVN的第一个提交id和git的第一个提交id,将它们回显到。git/info/grafts:echo "git_id svn_id}" > .git/info/grafts then git SVN dcommit 检查每一个git提交,复制文件到svn_repo, SVN提交

bash演示: github演示

v1。X:使用rebase和commit id

v2。X:使用复制文件,然后SVN提交

> SVN,具有完整的提交历史

我有一个Git项目,必须把它移到SVN上。这是我如何做到的,保持整个提交历史。唯一丢失的是原始提交时间,因为libSVN在执行git svn dcommit时将设置本地时间。

Howto:

Have a SVN repository where we want to import our stuff to and clone it with git-svn: git svn clone https://path.to/svn/repository repo.git-svn` Go there: cd repo.git-svn Add the remote of the Git repository (in this example I'm using C:/Projects/repo.git). You want to push to SVN and give it the name old-git: git remote add old-git file:///C/Projects/repo.git/ Fetch the information from the master branch from the old-git repository to the current repository: git fetch old-git master Checkout the master branch of the old-git remote into a new branch called old in the current repository: git checkout -b old old-git/master` Rebase to put the HEAD on top of old-git/master. This will maintain all your commits. What this does basically is to take all of your work done in Git and put it on top of the work you are accessing from SVN. git rebase master Now go back to your master branch: git checkout master And you can see that you have a clean commit history. This is what you want to push to SVN. Push your work to SVN: git svn dcommit

这是所有。这是非常干净的,没有黑客,一切工作完美的开箱即用。享受。

下面是我们如何做到的:

在你的机器上克隆你的Git存储库。

打开.git/config并添加以下内容(来自维护Git存储库的只读SVN镜像):

[svn-remote "svn"]
    url = https://your.svn.repo
    fetch = :refs/remotes/git-svn

现在,在控制台窗口中输入以下内容:

git svn fetch svn
git checkout -b svn git-svn
git merge master

现在,如果它因为某种原因在这里中断了,输入这三行:

git checkout --theirs .
git add .
git commit -m "some message"

最后,您可以提交到SVN:

git svn dcommit

注意:我总是在事后丢弃那个文件夹。