1#!/bin/sh 2 3USAGE='[-f] [-b <new_branch>] [-m] [<branch>] [<paths>...]' 4SUBDIRECTORY_OK=Sometimes 5. git-sh-setup 6 7old_name=HEAD 8old=$(git-rev-parse --verify $old_name 2>/dev/null) 9new= 10new_name= 11force= 12branch= 13newbranch= 14newbranch_log= 15merge= 16while["$#"!="0"];do 17 arg="$1" 18shift 19case"$arg"in 20"-b") 21 newbranch="$1" 22shift 23[-z"$newbranch"] && 24 die "git checkout: -b needs a branch name" 25 git-show-ref --verify --quiet --"refs/heads/$newbranch"&& 26 die "git checkout: branch$newbranchalready exists" 27 git-check-ref-format"heads/$newbranch"|| 28 die "git checkout: we do not like '$newbranch' as a branch name." 29;; 30"-l") 31 newbranch_log=1 32;; 33"-f") 34 force=1 35;; 36-m) 37 merge=1 38;; 39--) 40break 41;; 42-*) 43 usage 44;; 45*) 46ifrev=$(git-rev-parse --verify "$arg^0" 2>/dev/null) 47then 48if[-z"$rev"];then 49echo"unknown flag$arg" 50exit1 51fi 52 new="$rev" 53 new_name="$arg^0" 54if git-show-ref --verify --quiet --"refs/heads/$arg" 55then 56 branch="$arg" 57fi 58elifrev=$(git-rev-parse --verify "$arg^{tree}" 2>/dev/null) 59then 60# checking out selected paths from a tree-ish. 61 new="$rev" 62 new_name="$arg^{tree}" 63 branch= 64else 65 new= 66 new_name= 67 branch= 68set x "$arg""$@" 69shift 70fi 71case"$1"in 72--) 73shift;; 74esac 75break 76;; 77esac 78done 79 80case"$force$merge"in 8111) 82 die "git checkout: -f and -m are incompatible" 83esac 84 85# The behaviour of the command with and without explicit path 86# parameters is quite different. 87# 88# Without paths, we are checking out everything in the work tree, 89# possibly switching branches. This is the traditional behaviour. 90# 91# With paths, we are _never_ switching branch, but checking out 92# the named paths from either index (when no rev is given), 93# or the named tree-ish (when rev is given). 94 95iftest"$#"-ge1 96then 97 hint= 98iftest"$#"-eq1 99then 100 hint=" 101Did you intend to checkout '$@' which can not be resolved as commit?" 102fi 103iftest''!="$newbranch$force$merge" 104then 105 die "git checkout: updating paths is incompatible with switching branches/forcing$hint" 106fi 107iftest''!="$new" 108then 109# from a specific tree-ish; note that this is for 110# rescuing paths and is never meant to remove what 111# is not in the named tree-ish. 112 git-ls-tree --full-name -r"$new""$@"| 113 git-update-index --index-info||exit $? 114fi 115 git-checkout-index -f -u --"$@" 116exit $? 117else 118# Make sure we did not fall back on $arg^{tree} codepath 119# since we are not checking out from an arbitrary tree-ish, 120# but switching branches. 121iftest''!="$new" 122then 123 git-rev-parse --verify"$new^{commit}">/dev/null 2>&1|| 124 die "Cannot switch branch to a non-commit." 125fi 126fi 127 128# We are switching branches and checking out trees, so 129# we *NEED* to be at the toplevel. 130cdup=$(git-rev-parse --show-cdup) 131iftest!-z"$cdup" 132then 133cd"$cdup" 134fi 135 136[-z"$new"] && new=$old&& new_name="$old_name" 137 138# If we don't have an old branch that we're switching to, 139# and we don't have a new branch name for the target we 140# are switching to, then we'd better just be checking out 141# what we already had 142 143[-z"$branch$newbranch"] && 144["$new"!="$old"] && 145 die "git checkout: to checkout the requested commit you need to specify 146 a name for a new branch which is created and switched to" 147 148if["X$old"= X ] 149then 150echo"warning: You do not appear to currently be on a branch.">&2 151echo"warning: Forcing checkout of$new_name.">&2 152 force=1 153fi 154 155if["$force"] 156then 157 git-read-tree --reset -u$new 158else 159 git-update-index --refresh>/dev/null 160 merge_error=$(git-read-tree -m -u $old $new 2>&1)|| ( 161case"$merge"in 162'') 163echo>&2"$merge_error" 164exit1;; 165esac 166 167# Match the index to the working tree, and do a three-way. 168 git diff-files --name-only| git update-index --remove --stdin&& 169 work=`git write-tree`&& 170 git read-tree --reset -u$new&& 171 git read-tree -m -u --aggressive$old $new $work||exit 172 173if result=`git write-tree 2>/dev/null` 174then 175echo>&2"Trivially automerged." 176else 177 git merge-index -o git-merge-one-file -a 178fi 179 180# Do not register the cleanly merged paths in the index yet. 181# this is not a real merge before committing, but just carrying 182# the working tree changes along. 183 unmerged=`git ls-files -u` 184 git read-tree --reset$new 185case"$unmerged"in 186'') ;; 187*) 188( 189 z40=0000000000000000000000000000000000000000 190echo"$unmerged"| 191sed-e's/^[0-7]* [0-9a-f]* /'"0$z40/" 192echo"$unmerged" 193) | git update-index --index-info 194;; 195esac 196exit0 197) 198 saved_err=$? 199iftest"$saved_err"=0 200then 201test"$new"="$old"|| git diff-index --name-status"$new" 202fi 203(exit$saved_err) 204fi 205 206# 207# Switch the HEAD pointer to the new branch if we 208# checked out a branch head, and remove any potential 209# old MERGE_HEAD's (subsequent commits will clearly not 210# be based on them, since we re-set the index) 211# 212if["$?"-eq0];then 213if["$newbranch"];then 214if["$newbranch_log"];then 215mkdir-p$(dirname "$GIT_DIR/logs/refs/heads/$newbranch") 216touch"$GIT_DIR/logs/refs/heads/$newbranch" 217fi 218 git-update-ref -m"checkout: Created from$new_name""refs/heads/$newbranch"$new||exit 219 branch="$newbranch" 220fi 221["$branch"] && 222 GIT_DIR="$GIT_DIR" git-symbolic-ref HEAD "refs/heads/$branch" 223rm-f"$GIT_DIR/MERGE_HEAD" 224else 225exit1 226fi