It's not a bug, it's an undocumented feature. It should be documented as
"git-unpack-objects < $pack; rm $pack" is something one would deem correct at
first glance (luckily I just moved the pack away and did git-fsck-cache).
To write an object, git-unpack-objects ends in
unpack-objects.c:write_object -> sha1_file.c:write_sha1_file:
/* Normally if we have it in the pack then we do not bother writing
* it out into .git/objects/??/?{38} file.
*/
This indeed works, so the files aren't unpacked.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-
: 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