{"thread":{"id":"19645","subject":"Savannah Git repositories: do not panic","startedAt":"2009-06-02T21:55:48Z","lastAt":"2009-06-02T21:55:48Z","messageCount":1,"participants":["Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"115285","messageId":"alpine.DEB.1.00.0906022349120.26154@pacific.mpi-cbg.de","threadId":"19645","inReplyTo":null,"subject":"Savannah Git repositories: do not panic","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-06-02T21:55:48Z","receivedAt":"2009-06-02T21:55:48Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nI got aware of several projects who hosted a Git repository on Savannah \nbeing affected by their filesystem corruption.  The good Savannah \npeople put back some revisions from their backup, which are something \nlike a month old.\n\nSome people seem to think that it has adverse effects to fetch those \nobsolete branch revisions with a \"git fetch\".\n\nThis mail tries to serve to cool everybody down: nobody can take away from \nyou what you already fetched: in the default set up, you will still have \nthe \"reflogs\", i.e. \"git log -g origin/master\" will show you a \"forced \nupdate\" to the obsolete revision, but as the next commit, you will have \nthe most up-to-date revision you fetched before.\n\nAnd, oh, your local branches are unaffected.\n\nYou can even help the project maintainers if you have a newer revision \nthan is the current revision on Savannah...\n\nCiao,\nDscho\n\nP.S.: congratulations to everybody who switched to a distributed version \ncontrol system before this corruption...\n"}]}