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

Re: Inspecting a corrupt git object

From
HHHolger Hellmuth <hellmuth@ira.uka.de>
Date
Aug 4, 2010, 11:11 UTC
Message-ID
<4C594AE3.4000708@ira.uka.de>
In-Reply-To
<20100804092530.GA30070@jpl.local>
Magnus Bäck schrieb:
> Any other ideas why we would see such a difference? Hardware
> malfunction or memory corruption I guess, but something else?
> I can supply the actual object files if necessary.
> 
I checked with a repository here and all objects seem to start with 78
01. That means it is a common prefix. Ergo no malicious tampering, as
that would make only sense if the contents of the blob had changed.
So a random hardware or software malfunction is left as explanation IMHO
Holger
Previous: Magnus Bäck
Message 6 of 6 in “Inspecting a corrupt git object”
  1. Magnus BäckAug 4, 2010
  2. Alejandro Riveira FernándezAug 4, 2010
  3. Magnus BäckAug 4, 2010
  4. Thomas RastAug 4, 2010
  5. Magnus BäckAug 4, 2010
  6. Holger HellmuthAug 4, 2010

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.