From: Holger Hellmuth <hellmuth@ira.uka.de>
To: git@vger.kernel.org
Subject: Re: Inspecting a corrupt git object
Date: Wed, 04 Aug 2010 13:11:31 +0200 [thread overview]
Message-ID: <4C594AE3.4000708@ira.uka.de> (raw)
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
prev parent reply other threads:[~2010-08-04 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 9:25 Inspecting a corrupt git object Magnus Bäck
2010-08-04 9:48 ` Alejandro Riveira Fernández
2010-08-04 13:09 ` Magnus Bäck
2010-08-04 9:48 ` Thomas Rast
2010-08-04 13:02 ` Magnus Bäck
2010-08-04 11:11 ` Holger Hellmuth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C594AE3.4000708@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).