git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Yossi Leybovich <sleybo@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	git@vger.kernel.org, ae@op5.se,
	Yossi Leybovich <sleybo@mellanox.co.il>
Subject: Re: corrupt object on git-gc
Date: Fri, 9 Nov 2007 20:52:37 +0100	[thread overview]
Message-ID: <20071109195237.GA20030@glandium.org> (raw)
In-Reply-To: <4fe79b4b0711091141i38044a5o1ef940d9c7afd58f@mail.gmail.com>

On Fri, Nov 09, 2007 at 02:41:05PM -0500, Yossi Leybovich wrote:
> What I do notice is that this commit involve few files. most of the
> file the commit generate the right next SHA1
> only for one file its generate broken SHA1
> 
> From the git show <commit> I can see that the file which end up
> corrupted is actually being totaly remove from
> 
> diff --git a/SymmK/St.c b/SymmK/St.c
> index 308806c..4b9458b 100755
> --- a/SymmK/St.c
> +++ b/SymmK/St.c
> @@ -1,1535 +0,0 @@
> -MODULE_ALIAS(m_st);
> -
> -#include <errno.h>
> -#include <string.h>
> -#include <stdarg.h>
> -#include <sys/types.h>
> -#include <sys/time.h>
> -#include "ib_global_init.h"
> ....
> .....
> ....
> 
> 
> While I tried to delete the whole file and I did not get the right SHA1
> Is this soud familiar to some one ?
> maybe its releated to issue with some kind of white character I cant see.

Because the blob is corrupted, git show can't display the correct diff.
You have to guess it by yourself ! The best you can do is look at the
diff for this file between its previous version and the one just after
the corrupted version.

Mike

  reply	other threads:[~2007-11-09 19:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 13:38 corrupt object on git-gc Yossi Leybovich
2007-11-09 13:46 ` Andreas Ericsson
2007-11-09 15:01   ` Yossi Leybovich
2007-11-09 15:34     ` Johannes Sixt
2007-11-09 15:53       ` Yossi Leybovich
2007-11-09 16:03         ` Johannes Sixt
2007-11-09 16:03         ` Nicolas Pitre
2007-11-09 16:31           ` Yossi Leybovich
2007-11-09 16:52             ` Nicolas Pitre
2007-11-09 16:28 ` Linus Torvalds
2007-11-09 17:28   ` [PATCH] add a howto document about corrupted blob recovery Nicolas Pitre
2007-11-09 17:30     ` Johannes Schindelin
2007-11-26  2:12     ` J. Bruce Fields
2007-11-09 17:53   ` corrupt object on git-gc Yossi Leybovich
2007-11-09 18:02     ` Linus Torvalds
2007-11-09 18:37       ` Yossi Leybovich
2007-11-09 18:55         ` Linus Torvalds
2007-11-09 19:07           ` Mike Hommey
2007-11-09 19:41             ` Yossi Leybovich
2007-11-09 19:52               ` Mike Hommey [this message]
     [not found] <6C2C79E72C305246B504CBA17B5500C902535D9C@mtlexch01.mtl.com>
     [not found] ` <458BC6B0F287034F92FE78908BD01CE814472B3D@mtlexch01.mtl.com>
2007-11-08 23:59   ` Yossi Leybovich
2007-11-09  5:13     ` Christian Couder
2007-11-09 12:16       ` Yossi Leybovich
2007-11-09 17:45         ` Junio C Hamano
2007-11-09  8:10     ` Alex Riesen
2007-11-09 12:23       ` Yossi Leybovich
2007-11-09 12:56         ` Andreas Ericsson
2007-11-09 16:17       ` Nicolas Pitre

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=20071109195237.GA20030@glandium.org \
    --to=mh@glandium.org \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=sleybo@gmail.com \
    --cc=sleybo@mellanox.co.il \
    --cc=torvalds@linux-foundation.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).