git svn clone 运行很长时间、完成、什么也没完成是什么意思
我将 mac 上的 git 升级到了 1.7.2。我无法再让 git svn clone 或 git svn fetch 成功。
当 GIT_TRACE=2 时，该主题的最后一句话是：
trace: built-in: git 'config' 'svn-remote.svn.branches-maxRev' '12912'
trace: built-in: git 'config' 'svn-remote.svn.tags-maxRev' '12912'
trace: built-in: git 'config' 'svn-remote.svn.branches-maxRev' '12912'
trace: built-in: git 'config' 'svn-remote.svn.tags-maxRev' '12912'
trace: built-in: git 'gc' '--auto'
gitbranch -a 无话可说，没有检查出任何内容。但也没有错误消息。
git svn clone -s https://gate.svn.sourceforge.net/svnroot/gate
万一其他人愿意尝试这个。
我想我应该问一个问题：“有人知道解决这个问题的方法吗？”
编辑
这里有一个错误，但它与我声称的完全不同。我怀疑这和git版本有什么关系。
上面的 URL 不是 stdlayout svn url。如果您在末尾添加另一个 /gate，您将看到一个 stdlayout url。该错误是 git svn 应该打印一条消息，大意是找不到主干、标签、或分支。
I upgraded git on my mac to 1.7.2. I can no longer get git svn clone or git svn fetch to succeed.
With GIT_TRACE=2, the last words on the subject are:
trace: built-in: git 'config' 'svn-remote.svn.branches-maxRev' '12912'
trace: built-in: git 'config' 'svn-remote.svn.tags-maxRev' '12912'
trace: built-in: git 'config' 'svn-remote.svn.branches-maxRev' '12912'
trace: built-in: git 'config' 'svn-remote.svn.tags-maxRev' '12912'
trace: built-in: git 'gc' '--auto'
git branch -a has nothing to say, nothing is checked out. But no error messages, either.
git svn clone -s https://gate.svn.sourceforge.net/svnroot/gate
In case someone else care to try this.
I suppose I should ask a question: "Anyone know a way around this?"
EDIT
There is a bug here, but it's completely different from what I claimed. I doubt it has anything to do with the git version.
The URL above is not a stdlayout svn url. If you add another /gate to the end, you will be looking at a stdlayout url. The bug is that git svn should be printing a message to the effect that it cannot find trunk, tags, or branches.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我将把它扔在那里，因为我在一个具有很长的复杂分支历史记录（并且没有标准主干分支）的存储库上遇到了 git-svn 的类似问题。 Git-svn 花了很长时间，因为它试图确定历史向后遍历的开始。花了相当长的时间，最终因为这个SVN repo的分支历史的问题而失败。
使这一点变得可靠的原因是使用
-r {Rev ID start}..HEAD将我克隆的历史记录限制在特定范围内。也许这会有所帮助。I'll throw this out there because I ran into similar problems with git-svn on a repo that had a long complex branch history (and no standard trunk branch). Git-svn took a long time because it was trying to determine the start of history traversing backwards. It took quite a long time, and in the end failed due to problems in this SVN repo's branch history.
What helped make this reliable was to limit the history I cloned to a specific range using
-r {Rev ID start}..HEAD. Perhaps this will help.