author | Junio C Hamano <junkio@cox.net> | |
Sun, 25 Jun 2006 12:28:58 +0000 (05:28 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sun, 25 Jun 2006 12:28:58 +0000 (05:28 -0700) | ||
commit | 2ad47d61b93e4027bd20f71963dcf1429dccc1fa | |
tree | 6fc480d6f11ba66bf1ed90cadfd2a4b3bb3b2aa3 | tree | snapshot |
parent | 29f4ad867cd15f4029c280c417f4a0866d5229a9 | commit | diff |
git-repack: Be careful when updating the same pack as an existing one.
After a clone, packfiles are read-only by default and "mv" to
replace the pack with a new one goes interactive, asking if the
user wants to replace it. If one is successfully moved and the
other is not, the pack and its idx would become out-of-sync and
corrupts the repository.
Recovering is straightforward -- it is just the matter of
finding the remaining .tmp-pack-* and make sure they are both
moved -- but we should be extra careful not to do something so
alarming to the users.
Signed-off-by: Junio C Hamano <junkio@cox.net>
After a clone, packfiles are read-only by default and "mv" to
replace the pack with a new one goes interactive, asking if the
user wants to replace it. If one is successfully moved and the
other is not, the pack and its idx would become out-of-sync and
corrupts the repository.
Recovering is straightforward -- it is just the matter of
finding the remaining .tmp-pack-* and make sure they are both
moved -- but we should be extra careful not to do something so
alarming to the users.
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-repack.sh | diff | blob | history |