diff options
| author | tekkub <tekkub@gmail.com> | 2010-02-03 14:22:00 -0700 |
|---|---|---|
| committer | tekkub <tekkub@gmail.com> | 2010-02-03 14:22:00 -0700 |
| commit | 71e9d51850399e871261cd9b8da380432602a41d (patch) | |
| tree | 2a3490a0030573d26f02df884d53b6abef673c92 | |
| parent | 67fd47efb5b145d780ff3bd3058e50ec8962b756 (diff) | |
Add note about egit 0.7.0 potentially fixing the issue.
| -rw-r--r-- | _posts/2009-11-16-egit-corruption.markdown | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/_posts/2009-11-16-egit-corruption.markdown b/_posts/2009-11-16-egit-corruption.markdown index 7426c8b..62dfd04 100644 --- a/_posts/2009-11-16-egit-corruption.markdown +++ b/_posts/2009-11-16-egit-corruption.markdown @@ -5,7 +5,7 @@ description: How to fix corruption in a remote repo caused by egit categories: troubleshooting --- -Due to a bug in egit's impementation of the `git push` command, remote repos can become corrupted due to missing objects: +Due to a bug in egit's implementation of the `git push` command, remote repos can become corrupted due to missing objects: <pre class="terminal">$ git fsck broken link from commit 5b90a930763c442f0fc3d819685083b4eda69f8e @@ -14,6 +14,8 @@ missing commit e1ea55d308b7808cb982f509c8dfa199ada4677e</pre> 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 may be fixed in egit 0.7.0. We recommend updating and trying the following commands from egit before resorting to the commandline._ + Correcting the remote repo -------------------------- |