Skip to content

Commit

Permalink
git-merge-one-file: resurrect leading path creation.
Browse files Browse the repository at this point in the history
Since we do not use git-update-index followed by
git-checkout-index -u to create the half-merged file on
conflicting case anymore, we need to make sure the leading
directories are created here.

Maybe a better solution would be to allow update-index to add to
higher stage, and checkout-index to extract from such, but that
is a change slightly bigger than I would like to have so close
to 1.0, so this should do for now.

Signed-off-by: Junio C Hamano <junkio@cox.net>
  • Loading branch information
Junio C Hamano committed Dec 6, 2005
1 parent bb6d7b8 commit be61db9
Showing 1 changed file with 10 additions and 2 deletions.
12 changes: 10 additions & 2 deletions git-merge-one-file.sh
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,14 @@
# been handled already by git-read-tree, but that one doesn't
# do any merges that might change the tree layout.

verify_path() {
file="$1"
dir=`dirname "$file"` &&
mkdir -p "$dir" &&
rm -f -- "$file" &&
: >"$file"
}

case "${1:-.}${2:-.}${3:-.}" in
#
# Deleted in both or deleted in one and unchanged in the other
Expand Down Expand Up @@ -90,9 +98,9 @@ case "${1:-.}${2:-.}${3:-.}" in
# Create the working tree file, with the correct permission bits.
# we can not rely on the fact that our tree has the path, because
# we allow the merge to be done in an unchecked-out working tree.
rm -f "$4" &&
verify_path "$4" &&
git-cat-file blob "$2" >"$4" &&
case "$6" in *7??) chmod +x "$4" ;; esac &&
case "$6" in *7??) chmod +x -- "$4" ;; esac &&
merge "$4" "$orig" "$src2"
ret=$?
rm -f -- "$orig" "$src2"
Expand Down

0 comments on commit be61db9

Please sign in to comment.