On 07/07/11 23:04, Sascha Vogt wrote:
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 was using egit 0.12.1 in Helios SR2 x86_64 under Linux. I uninstalled
egit on 8 June.
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.
http://lists.refractions.net/pipermail/udig-devel/2011-February/thread.html#19321
In particular, these:
http://lists.refractions.net/pipermail/udig-devel/2011-February/019321.html
http://lists.refractions.net/pipermail/udig-devel/2011-February/019329.html
http://lists.refractions.net/pipermail/udig-devel/2011-February/019334.html
http://lists.refractions.net/pipermail/udig-devel/2011-February/019346.html
The bug:
http://help.github.com/fix-egit-corruption/
******
Due to a bug in the EGit/JGit implementation of the git push command,
remote repos can become corrupted due to missing objects:
$ git fsck
broken link from commit 5b90a930763c442f0fc3d819685083b4eda69f8e
to commit e1ea55d308b7808cb982f509c8dfa199ada4677e
missing commit e1ea55d308b7808cb982f509c8dfa199ada4677e
This can prevent cloning and fetching from the repo. The objects were
never pushed to the remote repo, therefore support cannot recover the
repo directly for the user. The only solution is for the user that
pushed the commits to push them again from the command line.
This issue was fixed in EGit/JGit 0.8.4. We recommend updating and
trying the following commands from EGit/JGit before resorting to the
commandline.
[...]
******
--
Ben Caradoc-Davies <[email protected]>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
