Savannah now has a monthly cron job that does some git maintenance
on all repos (thanks to Jim Meyering). Does this suffice for your
Yes, partially (one of two) -- thanks!
(In June, i had somehow pushed an entirely separate dag into the ‘rcs’
repo (from a private repo). As a result, ‘git fsck --root’ showed two
lines, and of course, the private dag was accessible if one could guess
a valid commit id (SHA1). The fix is to remove all references and gc.
I did the former immediately, w/in 5 minutes of discovering the error,
and it looks to me that the script does the latter. I confirm that a
cgit (web) probe now yields "Bad object id", as expected. Cool!)
The other need (two of two), i will address in the other thread.
Thien-Thi Nguyen ..................................... GPG key: 4C807502
. NB: ttn at glug dot org is not me .
. (and has not been since 2007 or so) .
. ACCEPT NO SUBSTITUTES .
........... please send technical questions to mailing lists ...........