Hi, I'd like to check if there's any reason in the overall design of git which would make deleting tmp_pack's that have suffered write errors a bad idea? (Before I look further into this I may be missing a good reason why they shouldn't be auto-deleted.) My encounter with this comes from using an almost full usbstick which I discovered when I was poking around for other reasons several partial packs from occasions (separated by weeks) where gc failed. On each failure I'd removed stuff from the drive to clear space and done a successful gc but hadn't thought to check below .git for removable stuff so they'd just accumulated. Below is a output of a test session: $ git version git version 1.5.3.6 $ git gc --aggressive --prune Generating pack... Done counting 22216 objects. Deltifying 22216 objects... 100% (22216/22216) done Writing 22216 objects... fatal: sha1 file '/media/usbdiskc/v.git/objects/tmp_pack_QCYYAi' write error (No space left on device) error: failed to run repack $ ls -l /media/usbdiskc/v.git/objects/ total 3944 drwxr-xr-x 2 sis05dst sis05dst 2048 2007-11-28 07:25 info drwxr-xr-x 2 sis05dst sis05dst 2048 2007-11-28 07:25 pack -rwxr-xr-x 1 sis05dst sis05dst 4034560 2007-11-28 07:25 tmp_pack_QCYYAi -rw------- 1 sis05dst sis05dst 0 2007-04-18 23:02 tmp_pack_RYLguI -- cheers, dave tweed__________________________ david.tweed@xxxxxxxxx Rm 124, School of Systems Engineering, University of Reading. "we had no idea that when we added templates we were adding a Turing- complete compile-time language." -- C++ standardisation committee - 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
