1#!/bin/sh 2 3USAGE='[-f] [-b <new_branch>] [-m] [<branch>] [<paths>...]' 4SUBDIRECTORY_OK=Sometimes 5. git-sh-setup 6require_work_tree 7 8old_name=HEAD 9old=$(git-rev-parse --verify $old_name 2>/dev/null) 10oldbranch=$(git-symbolic-ref $old_name 2>/dev/null) 11new= 12new_name= 13force= 14branch= 15newbranch= 16newbranch_log= 17merge= 18LF=' 19' 20while["$#"!="0"];do 21 arg="$1" 22shift 23case"$arg"in 24"-b") 25 newbranch="$1" 26shift 27[-z"$newbranch"] && 28 die "git checkout: -b needs a branch name" 29 git-show-ref --verify --quiet --"refs/heads/$newbranch"&& 30 die "git checkout: branch$newbranchalready exists" 31 git-check-ref-format"heads/$newbranch"|| 32 die "git checkout: we do not like '$newbranch' as a branch name." 33;; 34"-l") 35 newbranch_log=1 36;; 37"-f") 38 force=1 39;; 40-m) 41 merge=1 42;; 43--) 44break 45;; 46-*) 47 usage 48;; 49*) 50ifrev=$(git-rev-parse --verify "$arg^0" 2>/dev/null) 51then 52if[-z"$rev"];then 53echo"unknown flag$arg" 54exit1 55fi 56 new="$rev" 57 new_name="$arg" 58if git-show-ref --verify --quiet --"refs/heads/$arg" 59then 60 branch="$arg" 61fi 62elifrev=$(git-rev-parse --verify "$arg^{tree}" 2>/dev/null) 63then 64# checking out selected paths from a tree-ish. 65 new="$rev" 66 new_name="$arg^{tree}" 67 branch= 68else 69 new= 70 new_name= 71 branch= 72set x "$arg""$@" 73shift 74fi 75case"$1"in 76--) 77shift;; 78esac 79break 80;; 81esac 82done 83 84case"$force$merge"in 8511) 86 die "git checkout: -f and -m are incompatible" 87esac 88 89# The behaviour of the command with and without explicit path 90# parameters is quite different. 91# 92# Without paths, we are checking out everything in the work tree, 93# possibly switching branches. This is the traditional behaviour. 94# 95# With paths, we are _never_ switching branch, but checking out 96# the named paths from either index (when no rev is given), 97# or the named tree-ish (when rev is given). 98 99iftest"$#"-ge1 100then 101 hint= 102iftest"$#"-eq1 103then 104 hint=" 105Did you intend to checkout '$@' which can not be resolved as commit?" 106fi 107iftest''!="$newbranch$force$merge" 108then 109 die "git checkout: updating paths is incompatible with switching branches/forcing$hint" 110fi 111iftest''!="$new" 112then 113# from a specific tree-ish; note that this is for 114# rescuing paths and is never meant to remove what 115# is not in the named tree-ish. 116 git-ls-tree --full-name -r"$new""$@"| 117 git-update-index --index-info||exit $? 118fi 119 120# Make sure the request is about existing paths. 121 git-ls-files --error-unmatch --"$@">/dev/null ||exit 122 git-ls-files --"$@"| 123 git-checkout-index -f -u --stdin 124exit $? 125else 126# Make sure we did not fall back on $arg^{tree} codepath 127# since we are not checking out from an arbitrary tree-ish, 128# but switching branches. 129iftest''!="$new" 130then 131 git-rev-parse --verify"$new^{commit}">/dev/null 2>&1|| 132 die "Cannot switch branch to a non-commit." 133fi 134fi 135 136# We are switching branches and checking out trees, so 137# we *NEED* to be at the toplevel. 138cd_to_toplevel 139 140[-z"$new"] && new=$old&& new_name="$old_name" 141 142# If we don't have an existing branch that we're switching to, 143# and we don't have a new branch name for the target we 144# are switching to, then we are detaching our HEAD from any 145# branch. However, if "git checkout HEAD" detaches the HEAD 146# from the current branch, even though that may be logically 147# correct, it feels somewhat funny. More importantly, we do not 148# want "git checkout" nor "git checkout -f" to detach HEAD. 149 150detached= 151detach_warn= 152 153iftest -z"$branch$newbranch"&&test"$new"!="$old" 154then 155 detached="$new" 156iftest -n"$oldbranch" 157then 158 detach_warn="warning: you are not on ANY branch anymore. 159If you meant to create a new branch from the commit, you need -b to 160associate a new branch with the wanted checkout. Example: 161 git checkout -b <new_branch_name>$arg" 162fi 163eliftest -z"$oldbranch"&&test -n"$branch" 164then 165# Coming back... 166iftest -z"$force" 167then 168 git show-ref -d -s|grep"$old">/dev/null || { 169echo>&2 \ 170"You are not on any branch and switching to branch '$new_name' 171may lose your changes. At this point, you can do one of two things: 172 (1) Decide it is Ok and say 'git checkout -f$new_name'; 173 (2) Start a new branch from the current commit, by saying 174 'git checkout -b <branch-name>'. 175Leaving your HEAD detached; not switching to branch '$new_name'." 176exit1; 177} 178fi 179fi 180 181if["X$old"= X ] 182then 183echo>&2"warning: You appear to be on a branch yet to be born." 184echo>&2"warning: Forcing checkout of$new_name." 185 force=1 186fi 187 188if["$force"] 189then 190 git-read-tree --reset -u$new 191else 192 git-update-index --refresh>/dev/null 193 merge_error=$(git-read-tree -m -u --exclude-per-directory=.gitignore $old $new 2>&1)|| ( 194case"$merge"in 195'') 196echo>&2"$merge_error" 197exit1;; 198esac 199 200# Match the index to the working tree, and do a three-way. 201 git diff-files --name-only| git update-index --remove --stdin&& 202 work=`git write-tree`&& 203 git read-tree --reset -u$new&& 204eval GITHEAD_$new=${new_name:-${branch:-$new}} GITHEAD_$work=local&& 205export GITHEAD_$new GITHEAD_$work&& 206 git merge-recursive$old--$new $work||exit 207 208if result=`git write-tree 2>/dev/null` 209then 210echo>&2"Trivially automerged." 211else 212 git merge-index -o git-merge-one-file -a 213fi 214 215# Do not register the cleanly merged paths in the index yet. 216# this is not a real merge before committing, but just carrying 217# the working tree changes along. 218 unmerged=`git ls-files -u` 219 git read-tree --reset$new 220case"$unmerged"in 221'') ;; 222*) 223( 224 z40=0000000000000000000000000000000000000000 225echo"$unmerged"| 226sed-e's/^[0-7]* [0-9a-f]* /'"0$z40/" 227echo"$unmerged" 228) | git update-index --index-info 229;; 230esac 231exit0 232) 233 saved_err=$? 234iftest"$saved_err"=0 235then 236test"$new"="$old"|| git diff-index --name-status"$new" 237fi 238(exit$saved_err) 239fi 240 241# 242# Switch the HEAD pointer to the new branch if we 243# checked out a branch head, and remove any potential 244# old MERGE_HEAD's (subsequent commits will clearly not 245# be based on them, since we re-set the index) 246# 247if["$?"-eq0];then 248if["$newbranch"];then 249if["$newbranch_log"];then 250mkdir-p$(dirname "$GIT_DIR/logs/refs/heads/$newbranch") 251touch"$GIT_DIR/logs/refs/heads/$newbranch" 252fi 253 git-update-ref -m"checkout: Created from$new_name""refs/heads/$newbranch"$new||exit 254 branch="$newbranch" 255fi 256iftest -n"$branch" 257then 258 GIT_DIR="$GIT_DIR" git-symbolic-ref HEAD "refs/heads/$branch" 259eliftest -n"$detached" 260then 261# NEEDSWORK: we would want a command to detach the HEAD 262# atomically, instead of this handcrafted command sequence. 263# Perhaps: 264# git update-ref --detach HEAD $new 265# or something like that... 266# 267echo"$detached">"$GIT_DIR/HEAD.new"&& 268mv"$GIT_DIR/HEAD.new""$GIT_DIR/HEAD"|| 269 die "Cannot detach HEAD" 270iftest -n"$detach_warn" 271then 272echo>&2"$detach_warn" 273fi 274fi 275rm-f"$GIT_DIR/MERGE_HEAD" 276else 277exit1 278fi