summaryrefslogtreecommitdiff
path: root/builtin-verify-pack.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2008-06-25 05:41:34 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-06-25 06:23:21 (GMT)
commit8e21d63b02f1b26f7695ca515e51e4622a995af2 (patch)
tree18b2bb7cb8242bf68ce9ffe798f1fe03f2e46802 /builtin-verify-pack.c
parentf98f8cbac01e0d5dbb30660d7ea70af6a1439dfd (diff)
downloadgit-8e21d63b02f1b26f7695ca515e51e4622a995af2.zip
git-8e21d63b02f1b26f7695ca515e51e4622a995af2.tar.gz
git-8e21d63b02f1b26f7695ca515e51e4622a995af2.tar.bz2
clone: create intermediate directories of destination repo
The shell version used to use "mkdir -p" to create the repo path, but the C version just calls "mkdir". Let's replicate the old behavior. We have to create the git and worktree leading dirs separately; while most of the time, the worktree dir contains the git dir (as .git), the user can override this using GIT_WORK_TREE. We can reuse safe_create_leading_directories, but we need to make a copy of our const buffer to do so. Since merge-recursive uses the same pattern, we can factor this out into a global function. This has two other cleanup advantages for merge-recursive: 1. mkdir_p wasn't a very good name. "mkdir -p foo/bar" actually creates bar, but this function just creates the leading directories. 2. mkdir_p took a mode argument, but it was completely ignored. Acked-by: Daniel Barkalow <barkalow@iabervon.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin-verify-pack.c')
0 files changed, 0 insertions, 0 deletions