git-svn：rebase 失败多次然后工作
我们正在客户上推出 git，以便与中央 SVN 存储库进行交互。在大多数工作站上它工作得很好，但我们有一个工作站，人们必须运行 git svn rebase 3-4 次才能完成。每次都没有错误，但随机文件被标记为已修改或新的。这些文件似乎是从中央 svn 存储库中提取但尚未完成的提交。再次重新运行 git svn rebase 几次可以解决这个问题。该计算机是顶级的，具有充足的硬盘空间和 16 GB 内存。还有其他人遇到过这样的问题吗？
We are rolling out git on our clients to interact with a central SVN repository. On most work stations it works fine, but we have one work station where the person has to run git svn rebase 3-4 times before it completes. Each time there is no error, but random files are marks as modified or new. The files seem to be a commit that was pulled down from the central svn repository but not completed. Rerunning git svn rebase again a few times clears this up. The computer is top of the line with plenty of hard drive space and 16 gigs ram. Has anyone else ran into issues like this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我有一个类似的问题，通过升级到 git 1.8 解决了。
为什么“git rebase”在阶段和工作副本中留下相反的修改集？
也许你应该尝试一下。
I had a similar issue that was solved by upgrading to git 1.8.
Why does "git rebase" leave opposite sets of modifications in the stage and the working copy?
Maybe you should try that.