为什么git-svn尝试使用旧的分支点? [英] Why is git-svn trying to use an old branch point?

问题描述

我正在尝试更多地依赖git-svn来完成所有任务，而不仅仅是在本地使用git，然后使用svn来处理服务器分支和标签.

I'm trying to rely more heavily on git-svn for all my tasks, rather than just use git locally and then svn to handle server branches and tags.

我对svn存储库做了一个全新的克隆.我必须从一个最近的修订版本(大约300个修订版本)开始，以防克隆需要几天的时间. git svn fetch和git svn dcommit都可以正常工作.

I did a brand new clone of my svn repository. I had to start from a fairly recent (300 revisions or so back) revision to prevent it taking days to clone. git svn fetch and git svn dcommit are all working fine.

我正在尝试使用我们的最新内部版本号3.6.1进行标记.因此，我要进行试运行:

I'm trying to tag with our latest build number, 3.6.1. So to do a dry-run I issue:

$ git svn tag -n -m "3.6.1 build" 3.6.1
Copying https://svnserver:8443/svn/TheProject/trunk at r5735 to https://svnserver:8443/svn/TheProject/tags/3.6.1...
branch_from: /tags => /tags/3.3.5
Found possible branch point: https://svnserver:8443/svn/TheProject/tags/3.3.5 => https://svnserver:8443/svn/TheProject/tags/3.3.5, 5726
Initializing parent: refs/remotes/tags/3.3.5@5726
Found possible branch point: https://svnserver:8443/svn/TheProject/trunk => https://svnserver:8443/svn/TheProject/tags/3.3.5, 2309
...I cancel as it starts listing all the files it'll add to svn...

我真的不明白这里发生了什么.为什么到目前为止要确定分支点呢?有什么问题吗?

I don't really get what's happening here. Why is it going back so far to determine a branch point? Is there something wrong?

推荐答案

我仍然不确定为什么需要它，但是看起来它需要"git svn fetch"，所以git在知道其他分支和标签之前就知道了做新的. (长时间运行)获取之后，它就可以完美地进行分支/标记.

I'm still unsure WHY it needed it, but it looks like it needed a "git svn fetch" so git knew about other branches and tags before it could do the new one. After that (long-running) fetch, it's able to branch/tag perfectly.

这篇关于为什么git-svn尝试使用旧的分支点?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！