From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: git@vger.kernel.org
Subject: Re: Inspecting a corrupt git object
Date: Wed, 4 Aug 2010 09:48:11 +0000 (UTC) [thread overview]
Message-ID: <i3bd0r$g2l$1@dough.gmane.org> (raw)
In-Reply-To: 20100804092530.GA30070@jpl.local
On Wed, 04 Aug 2010 11:25:30 +0200, Magnus Bäck wrote:
[ ... ]
>
> From what I gather from the community book and Pro Git, a git object
> file is a deflated representation of the object type as a string, the
> payload size, a null byte, and the payload. Is there a standard tool for
> inflating the file back so that I can inspect what the actual difference
> between these two are? Short of writing a tool utilizing zlib, at least.
Maybe
git cat-file -p <sha1>
?
>
> 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.
Alejandro
next prev parent reply other threads:[~2010-08-04 9:48 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 [this message]
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
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='i3bd0r$g2l$1@dough.gmane.org' \
--to=ariveira@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.