Blaisorblade [off-list ref] wrote:
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.
Funny, I just did the exact same thing today, scratched my head and
said ``what did I just do!?!?!'' as I had deleted the pack before
discovering that nothing was actually unpacked. *sigh* At least
it was a clone of the real repository and thus didn't matter to me.
I totally didn't expect that behavior. But I should have. It makes
perfect sense.
--
Shawn.