git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Magnus Bäck" <magnus.back@sonyericsson.com>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Inspecting a corrupt git object
Date: Wed, 4 Aug 2010 15:09:57 +0200	[thread overview]
Message-ID: <20100804130957.GB1537@jpl.local> (raw)
In-Reply-To: <i3bd0r$g2l$1@dough.gmane.org>

On Wednesday, August 04, 2010 at 11:48 CEST,
     Alejandro Riveira Fernández <ariveira@gmail.com> wrote:

> 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>
>
>  ?

Sorry, I should've been more clear here. I know about cat-file's
pretty-printing abilities, but I just wanted to inflate the loose
object data and see *exactly* where the differing byte ended up.

-- 
Magnus Bäck                      Opinions are my own and do not necessarily
SW Configuration Manager         represent the ones of my employer, etc.
Sony Ericsson

  reply	other threads:[~2010-08-04 13:10 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 [this message]
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=20100804130957.GB1537@jpl.local \
    --to=magnus.back@sonyericsson.com \
    --cc=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 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).