modification of sources file causes git corruption.

Matt McCutchen matt at mattmccutchen.net
Mon Aug 2 01:56:32 UTC 2010


On Sun, 2010-08-01 at 20:54 -0400, Dave Jones wrote:
> On Sat, Jul 31, 2010 at 10:58:26PM -0700, Matt McCutchen wrote:
> 
>  > That's not "corruption", that's just an unreferenced object, which does
>  > no harm except to waste space.  "git gc" will delete such objects.
>  
> (20:50:18:davej at gelk:kernel)$ git fsck --full
> dangling blob 41bc432a23a83d5775562572936792fc25aa9380
> (20:50:29:davej at gelk:kernel)$ git gc
> Counting objects: 395, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (274/274), done.
> Writing objects: 100% (395/395), done.
> Total 395 (delta 119), reused 388 (delta 115)
> (20:50:31:davej at gelk:kernel)$ git fsck --full
> dangling blob 41bc432a23a83d5775562572936792fc25aa9380

Sorry, I forgot to mention you need "git gc --prune=now".

> They may be harmless, but if something was to go wrong, they'd make figuring
> out what happened more complicated.

I'm not sure this is a legitimate concern.  What specific failure case
are you envisioning?

-- 
Matt



More information about the devel mailing list