Re: can't push to binutils-gdb, git-hooks rejecting commits

[Joel Brobecker <brobecker at adacore dot com>]

> I'm running it now... I'll let everyone know if anything turns up
> (just letting everyone know to avoid multiple people repeating
> the same effort).

The first run of "git fsck" reported a number of dangling
commits, which can be normal:

     /git/binutils-gdb.git % git fsck
     dangling commit b376a372a6a884258517ca0e4074c44497b52e2d
     dangling commit e0b06424ffba39b97c5bcf75c1d56d1da39a1d76
     dangling commit b325e68abacbefa85b3a9ed928e9d989f150a9a9
     dangling commit 9b4ac9ab75b1941fd3f340240c56bf4f6a73816e
     dangling commit 2f8c2964d70f6fb0a0223d82dafdcaf5c60736a6
     dangling commit dc044a14027136c864d69c83598f3ba37c44fc9c
     dangling commit 70700c92be133d5b144a34c3a3bc11401bc746f4
     dangling commit b97c8e894e84f67560cc520e3b2c95e44fca5591
     dangling commit 9dd2eee60fd96cce402319a03d4d41a9cb781ae6
     dangling commit 471a2f625914dda90a3188e7adc871ce8ab68021
     dangling commit 3575703e8e24fd37d59452a567a74faca7a7f099
     dangling commit 5ce8d065bc9f0fe02c0fe2ad1ab321a145a6f3b8
     dangling commit 028e31e41c75a03a9a4a4f32d8659c7253e541d8
     dangling commit 9bc99112bf8baa35080b89f76f7594fe5f578d47
     dangling commit 4d2b345dd00dc2d681ab65733b79edcaaf118201
     dangling commit 4edbf4492560418a8981389f2a121f5d413c2956
     dangling commit 3730b7a6c6b490386b6bb35bcfbb64692e056059
     dangling commit 910dd8d20edfab20b589f0844d1ba167df3886a5
     dangling commit bf2cd8bd1bf0ce196a2e22bafa83eb5a2e918e68
     dangling commit 5a2659aecf698e7ec457e198139b0ae55cd24d4c
     dangling commit 7695993f6c0b379f69c955c93ddacc0a32fa3531
     dangling commit 48283a3eb56bfba30c5430d31a22d9ab60f02367
     dangling commit 4563fa4ef6449402b2c01f0a3e847004e48f9e6c
     dangling commit 57db1a42615d23e5dd4892e50baeb8e50de7b35f
     dangling commit 3bdf1a7669b5ac083d21ebb6269010c970e00511
     dangling commit 80d27d03fd16f97f709ce37e20607f09624b633d
     dangling commit 1104df157fa02eab8d0688f2870183e787b98b7e
     dangling commit 7e7dffec482bba8fad3f963bfd0c9bfbb5873c74

I did a quick "git gc"...

     /git/binutils-gdb.git % git gc
     Counting objects: 914618, done.
     Delta compression using up to 16 threads.
     Compressing objects: 100% (143171/143171), done.
     Writing objects: 100% (914618/914618), done.
     Total 914618 (delta 760464), reused 913469 (delta 759471)

... which took care of a number of them, but (as expected)
still kept around the more recent commits:

     /git/binutils-gdb.git % git fsck
     dangling commit b325e68abacbefa85b3a9ed928e9d989f150a9a9
     dangling commit 9b4ac9ab75b1941fd3f340240c56bf4f6a73816e
     dangling commit 70700c92be133d5b144a34c3a3bc11401bc746f4
     dangling commit 3575703e8e24fd37d59452a567a74faca7a7f099
     dangling commit 028e31e41c75a03a9a4a4f32d8659c7253e541d8
     dangling commit 5a2659aecf698e7ec457e198139b0ae55cd24d4c
     dangling commit 7695993f6c0b379f69c955c93ddacc0a32fa3531
     dangling commit 48283a3eb56bfba30c5430d31a22d9ab60f02367
     dangling commit 3bdf1a7669b5ac083d21ebb6269010c970e00511
     dangling commit 7e7dffec482bba8fad3f963bfd0c9bfbb5873c74

In any case, looks like all references are now OK, and "git fsck"
did not detect any further issues in the repository.

-- 
Joel