aboutsummaryrefslogtreecommitdiff
path: root/git-rebase--am.sh
diff options
context:
space:
mode:
authorMichael Haggerty <mhagger@alum.mit.edu>2014-01-06 14:45:27 +0100
committerJunio C Hamano <gitster@pobox.com>2014-01-06 09:34:22 -0800
commit18d37e860dfb9a98fb93ea7bb517ec3c16f995c4 (patch)
tree4b2489b8538ac71aeacf45a3c7604c71b626f210 /git-rebase--am.sh
parentf3565c0ca535d3becdcd2266002385709ddfa66c (diff)
downloadgit-18d37e860dfb9a98fb93ea7bb517ec3c16f995c4.tar.gz
git-18d37e860dfb9a98fb93ea7bb517ec3c16f995c4.tar.xz
safe_create_leading_directories(): add new error value SCLD_VANISHED
Add a new possible error result that can be returned by safe_create_leading_directories() and safe_create_leading_directories_const(): SCLD_VANISHED. This value indicates that a file or directory on the path existed at one point (either it already existed or the function created it), but then it disappeared. This probably indicates that another process deleted the directory while we were working. If SCLD_VANISHED is returned, the caller might want to retry the function call, as there is a chance that a new attempt will succeed. Why doesn't safe_create_leading_directories() do the retrying internally? Because an empty directory isn't really ever safe until it holds a file. So even if safe_create_leading_directories() were absolutely sure that the directory existed before it returned, there would be no guarantee that the directory still existed when the caller tried to write something in it. Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-rebase--am.sh')
0 files changed, 0 insertions, 0 deletions