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

Re: corrupted Git repository

From
ILIlari Liusvaara <ilari.liusvaara@elisanet.fi>
Date
Jun 21, 2011, 10:39 UTC
Message-ID
<20110621103947.GA30147@LK-Perkele-VI.localdomain>
In-Reply-To
<BANLkTi=GdEfXnAGa6V-33wqX2C-2x-9JQQ@mail.gmail.com>
On Tue, Jun 21, 2011 at 02:40:47PM +0430, Kasra Khosoussi wrote:
Show 6 quoted lines
> Thanks for your help.
> 
> I used update-ref and changed refs/heads/master to the sha1 of
> previous commit. Then I commit the changes. Everything seems fine now
> except (as you previously mentioned), git fsck -full complains about
> dangling trees. Is it critical?
 
Dangling trees are normal. They are not errors.
-Ilari
Previous: Kasra KhosoussiNext: Kasra Khosoussi
Message 6 of 11 in “corrupted Git repository”
  1. Kasra KhosoussiJun 21, 2011
  2. Michael J GruberJun 21, 2011
  3. Kasra KhosoussiJun 21, 2011
  4. Michael J GruberJun 21, 2011
  5. Kasra KhosoussiJun 21, 2011
  6. Ilari LiusvaaraJun 21, 2011
  7. Kasra KhosoussiJun 21, 2011
  8. Johannes SixtJun 21, 2011
  9. Kasra KhosoussiJun 21, 2011
  10. Carlos Martín NietoJun 21, 2011
  11. Kasra KhosoussiJun 21, 2011

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.