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

Re: What's going on here? Bad repo, no error locally?

From
BDBryan Donlan <bdonlan@gmail.com>
Date
Apr 22, 2009, 04:21 UTC
Message-ID
<3e8340490904212121q4bf2e25dsf5673bff764895c9@mail.gmail.com>
In-Reply-To
<450196A1AAAE4B42A00A8B27A59278E70ACE053E@EXCHANGE.trad.tradestation.com>
On Tue, Apr 21, 2009 at 8:18 PM, John Dlugosz <JDlugosz@tradestation.com> wrote:
Show 9 quoted lines
> Developer B runs git fsck --full, gets no errors but one dangling blob.
> Does a push.  No errors.
> Now, on the upstream repo, I run fsck, and find a bunch of danglings (as
> always) and a missing blob.
> Any fetch from that repo will fail, due to that missing blob.
>
> What's going on?  How can I fix his local repository, other than blow it
> away and start over, and copy his current files over and rebuild the few
> commits of interest?

Extract the object on developer B's workstation: git cat-file blob <object ID> > blob.dat

Copy it to upstream, then do: git hash-object -w blob.dat

If all goes well, hash-object will give you back the blob's ID, and the repository will fsck cleanly again.

Previous: John DlugoszNext: John M. Dlugosz
Message 2 of 7 in “What's going on here? Bad repo, no error locally?”
  1. John DlugoszApr 22, 2009
  2. Bryan DonlanApr 22, 2009
  3. John M. DlugoszApr 22, 2009
  4. Bryan DonlanApr 22, 2009
  5. Junio C HamanoApr 22, 2009
  6. John DlugoszApr 22, 2009
  7. Brandon CaseyApr 22, 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.