git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Savannah Git repositories: do not panic

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 2, 2009, 21:55 UTC
Message-ID
<alpine.DEB.1.00.0906022349120.26154@pacific.mpi-cbg.de>
Hi,

I got aware of several projects who hosted a Git repository on Savannah being affected by their filesystem corruption. The good Savannah people put back some revisions from their backup, which are something like a month old.

Some people seem to think that it has adverse effects to fetch those obsolete branch revisions with a "git fetch".

This mail tries to serve to cool everybody down: nobody can take away from you what you already fetched: in the default set up, you will still have the "reflogs", i.e. "git log -g origin/master" will show you a "forced update" to the obsolete revision, but as the next commit, you will have the most up-to-date revision you fetched before.

And, oh, your local branches are unaffected.

You can even help the project maintainers if you have a newer revision than is the current revision on Savannah...

Ciao, Dscho

P.S.: congratulations to everybody who switched to a distributed version control system before this corruption...

Message 1 of 1 in “Savannah Git repositories: do not panic”
  1. Johannes SchindelinJun 2, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.