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

Re: Recovering from a bad object

From
jonsmirl@gmail.com <jonsmirl@gmail.com>
Date
May 22, 2011, 22:31 UTC
Message-ID
<BANLkTinPOYH_pJsFkbQHCb_H5GhyTn+xhg@mail.gmail.com>
In-Reply-To
<7vy61ywjpa.fsf@alter.siamese.dyndns.org>
Looks like the corrupt object is ok in the object store.
I checked out about 20 of the dangling objects. They all start off with...
commit aa96dc2459563fa362bc53597cb076d93bcc884a
Author: Jon Smirl <jonsmirl@gmail.com>
Date:   Sat Mar 19 13:30:55 2011 -0400
    refresh (create temporary patch)    d666137c5fe3ee4c4c812c706b1a3c539405ffd0

That's stgit leaving all those dangling references. I will experiment with the current stgit and see if it is still leaving the dangling references or if they are leftovers from an old bug.

-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Junio C HamanoNext: jonsmirl@gmail.com
Message 3 of 7 in “Recovering from a bad object”
  1. jonsmirl@gmail.comMay 21, 2011
  2. Junio C HamanoMay 22, 2011
  3. jonsmirl@gmail.comMay 22, 2011
  4. jonsmirl@gmail.comMay 22, 2011
  5. Junio C HamanoMay 23, 2011
  6. Enrico WeigeltSep 18, 2011
  7. jonsmirl@gmail.comSep 18, 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.