Hi, Am 05.07.2011 10:46, schrieb Ben Caradoc-Davies: > For large projects (>8000 source files) egit becomes painful: every time > a file is saved egit insists on making Eclipse refresh everything, which > results in multi-second hangs. None of the configurable refresh options > appear to fix this. Pure pain. I had to stop using it. When did you last test this? I think exactly this behaviour has greatly improved in one of the last releases (either 1.0 or 0.12.x). At least I saw some posts on the egit mailing list indicating that.
> I am reliably informed that "egit is responsible for corrupting the udig > repository last year - losing a lot of our project history". But I found > it to work quite well for read-only use. How can that happen? I mean, every dev should have a complete repository locally. If one push corrupts the server just get one of the devs repos and use that... Better than nothing. Anyway, some sort of backup should be done as well (which is not that hard, since the repos are self-contained). Anyway, this shouldn't be egits fault, but jgit, the Java git implementation. Maybe you can share some more details how the repo got corrupted. Greetings -Sascha- PS: No, I'm not involved in the egit project nor do I know any of the committers in person, just a happy user --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
