可以“git推送”吗?坚持同样的%?

发布于 2024-10-13 19:55:09 字数 565 浏览 6 评论 0原文

我开始使用 Git。我觉得有必要指出这不是我的选择。直到上个月,我发现 Git 难以理解,但基本上很稳定。 2010 年 12 月一周后,我发现我无法再推送到我们的“中央”存储库。该进程在写入对象时将达到 70%,然后挂起。我们没有 Git “专家”,但我询问了其他一些一直在使用它的人,并得到了一些建议的解决方案。 Logitech 网络摄像头出现问题,尝试从安全模式 9 进行推送(显然需要联网),使用 Git bash 中的命令行而不是 乌龟。没有一个起作用。我最终做的是卸载 msysgit 并重新安装它。这解决了问题。或者说我是这么想的。前几天又出现这个问题。我无法再“推送”到我们的存储库。

我想我可以计划从现在开始每个月重新安装 msysgit,但这对我来说似乎是一个很大的让步。 :-)

知道我能做些什么来解决这个问题,甚至排除故障吗?

I am starting to use Git. I feel it is important to point out that this was not my choice. I have found Git to be problematic to understand but largely stable, until last month. A week into Dec 2010 I found that I could no longer push to our "central" repository. The process would reach 70% on writing objects and then hang. We have no Git "experts", but I asked some of the other people that have been using it and was given a number of suggested resolutions. Issues with Logitech webcams, attempting to do the push from Safe Mode 9 (with networking obviously), using the command line in Git bash rather than Tortoise. None worked. What I ended up doing was uninstalling msysgit and reinstalling it. That resolved the issue. Or so I thought. A couple of days ago the issue recurred. I can no longer "push" to our repository.

I suppose I could just plan on reinstalling msysgit every month from now on, but that seems like to great a concession to me. :-)

Any idea what I can do to resolve this, or even troubleshoot it?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

转角预定愛 2024-10-20 19:55:09

托管位置可能存在问题。我自 2008 年以来一直使用 git (msysgit),从未遇到过这样的问题。不过,我建议将服务器托管在 Linux 虚拟机上。这使得事情变得更快,并且 gitolite 非常适合权限。

希望这有帮助。

There may be issues with where it is hosted. I've been using git (msysgit) since 2008 and never had such an issue. I would recommend hosting the server on a linux VM though. That's made things faster and gitolite is excellent for permissions.

Hope this helps.

慢慢从新开始 2024-10-20 19:55:09

事实证明,问题出在 Git 的版本上,而不是操作系统上。我已经安装了 Git 版本 1.7。?服务器运行版本 1.6.4。通过将我的客户端降级到 1.6.4,我没有遇到任何问题。感谢您对此的协助。我仍然认为我可能会回到 ClearCase,直到我的组织内对 Git 提供更多支持。至于 adymitruk 的评论“你无法击败 Git 使你能够做的事情。”,一般来说这可能是正确的,但在我的工作中,我发现 Git 相对于 SVN 没有什么优势。也许我还不够Geek。也许我只是像 Linus 所说的所有 SVN 用户一样愚蠢。

再次感谢
帕特奥

Turns out it was the version of Git, not the OS that was the issue. I had installed Git version 1.7.?. The Server was running version 1.6.4. Byt downgrading my client to 1.6.4 I have not had any issues. Thanks for your assistence on this. I still think I will likely go back to ClearCase until there is more support for Git within my organization. As for adymitruk's comment "You just can't beat what Git enables you to do.", that may be true in general, but I have seen little advantage of Git over SVN for my work. Maybe I am just not enough of a Geek. Maybe I am just stupid as Linus say all SVN users are.

Thanks again
Pat O

裂开嘴轻声笑有多痛 2024-10-20 19:55:09

看来这不是一个常见问题,所以我建议您尝试一系列测试来看看问题出现在哪里:

  • 在另一台机器(例如您工作伙伴的计算机)上设置远程存储库,看看是否可以完成事务到该存储库,看看是否是存储库问题或网络问题
  • 在另一个网络上尝试一下,看看代理服务器、NAT 等是否存在问题(不应该是问题,但谁知道您的工作网络是什么像)
  • 存储库是简单的目录/文件结构。尝试将远程存储库复制到闪存驱动器上,然后将其放入本地计算机并尝试在本地更新。这会从组件链中消除网络和更新方法(服务器、ssh 等),以查看存储库本身是否存在问题(可能已损坏)。

与其发布几乎无穷无尽的故障排除可能性的详尽列表,不如考虑您正在与之交互的系统的所有部分,并尝试通过替换其中的某些部分(即工具、本地存储库、远程存储库)来缩小问题范围。存储库、网络等)此外,请确保您正确使用这些工具 - 传输一些更改不应该花费很长时间。

It seems like this is not a common problem, so I suggest you attempt a series of tests to see where the problem occurs:

  • Set up a remote repository on another machine (such as your work companion's computer) and see if you can complete the transaction to that repository to see if it's a repository problem or network problem
  • Try it on another network to see if there's a problem with proxy servers, NAT, etc in the way (shouldn't be an issue, but who knows what your work network is like)
  • The repositories are simple directory/file structures. Try copying the remote repository onto a flash drive, and then put it in your local machine and try to update it locally. This eliminates the network and your update method (server, ssh, etc) from the chain of components to see if there's a problem with the repository itself (perhaps it's corrupted).

Rather than post an exhaustive list of troubleshooting possibilities which would be nearly endless, consider all the parts of the system you are interacting with and try to narrow down the problem by replacing parts of it (ie, the tool, your local repository, the remote repository, the network, etc, etc, etc) Also, make sure you are using the tools correctly - it shouldn't take a long time to transfer a few changes.

对你而言 2024-10-20 19:55:09

只是另一个数据点 - 这可能与问题有关msysgit 项目站点上的 457。有一个带有解决方法的补丁(从 2011 年 2 月开始),但截至今天(2011 年 6 月 13 日)他们尚未将其包含在版本中。

Just another datapoint -- this could be related to Issue 457 on the msysgit project site. There is a patch with a workaround (from Feb 2011), but as of today (June 13, 2011) they have not included it in a release.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文