https://bugs.kde.org/show_bug.cgi?id=379219
--- Comment #12 from mrnuke <mr.nuke...@gmail.com> --- NAK. That's not how git is designed to work. I can take a Ferrarri and drive it on a dirt road. It coming back all dinged and scratched is not something Ferrari has to fix. The interaction issue here is that operations on the HEAD are locking and non-atomic. If someone keeps bugging me when I use a torque wrench, I will get the wrong torque. It doesn't mean the wrench is out of calibration. The same applies to git. When the problem is tightening a nut, and the tool is a torque wrench. In our case, the problem is source control, and the to tool is git. Generally, when someone switches to a terminal to do git stuff, kdevelop loses the focus. now I'm not saying go ahead and implement a silly "suspend git commands when we lose focus" heuristic, but something does have to be done. Note that this issue did not happen with Kdevelop 4.x (or somewhere around the late 4.x releases), so this is most likely a regression that was introduced within the past year. As far as a user is concerned, recalibrating the torque wrench won't solve the problem. What will is firing the employee who bugs me. I don't think that telling git users to stop using Kdevelop is a sane approach, as I am pretty sure the git guys will rightfully say "this is not our problem". -- You are receiving this mail because: You are watching all bug changes.
