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:52 UTC
Message-ID
<3e8340490904212152w4e308cf1wa0d20d05df3cbb48@mail.gmail.com>
In-Reply-To
<gsm6tr$or7$1@ger.gmane.org>

On Wed, Apr 22, 2009 at 12:37 AM, John M. Dlugosz <ngnr63q02@sneakemail.com> wrote:

Show 17 quoted lines
> Bryan Donlan wrote:
>>
>> 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.
>
> Thanks, I was looking through the manual for that but wasn't sure how to put
> it together.
>
> But, what could be wrong with B's repo that makes this happen repetetly?  I
> assumed it was network SNAFU, but after restoring the upstream repo, his
> push did it again.

Theoretically, this should never happen :) Are you accessing the repo directly through a file share, or through a git-daemon connection? If the former, could something like a virus scanner be deleting loose objects, perhaps?

Previous: John M. DlugoszNext: Junio C Hamano
Message 4 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.