downgrade "packfile cannot be accessed" errors to warnings
commit58a6a9cc4397477a7d8b620165e651028cc0e3c9
authorJeff King <peff@peff.net>
Fri, 14 Oct 2011 18:04:16 +0000 (14 14:04 -0400)
committerJunio C Hamano <gitster@pobox.com>
Fri, 14 Oct 2011 18:43:09 +0000 (14 11:43 -0700)
tree79ecdaf8e79365abee1b8ea2342b656ba7a5aafc
parent4c08018204f95c492c0ad7b033b8f57ccc2e43f5
downgrade "packfile cannot be accessed" errors to warnings

These can happen if another process simultaneously prunes a
pack. But that is not usually an error condition, because a
properly-running prune should have repacked the object into
a new pack. So we will notice that the pack has disappeared
unexpectedly, print a message, try other packs (possibly
after re-scanning the list of packs), and find it in the new
pack.

Acked-by: Nicolas Pitre <nico@fluxnic.net>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/pack-objects.c
sha1_file.c