Re: corrupt object on git-gc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Fri, 9 Nov 2007, Yossi Leybovich wrote:
>
> What interesting is the second part of the experiment
> I tried to apply the same commit on this file and it leaded to different SHA1

Eh. That commit was basically corrupt, because the blob had gotten 
removed. I don't even understand how git diff-tree gave a diff with that 
file at all (side note: I'd also suggest you just use "git show <commit>" 
instead of that complex and _really_ old git-diff-tree incantation).

So no, you didn't "apply the same commit". 

But if you have the diff somewhere (perhaps email archive? you sent it to 
somebody?) or you can re-create it exactly, then..

		Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux