3 USAGE
='[-f] [-b <new_branch>] [-m] [<branch>] [<paths>...]'
4 SUBDIRECTORY_OK
=Sometimes
9 old
=$
(git-rev-parse
--verify $old_name 2>/dev
/null
)
10 oldbranch
=$
(git-symbolic-ref
$old_name 2>/dev
/null
)
20 while [ "$#" != "0" ]; do
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 $newbranch already exists"
31 git-check-ref-format
"heads/$newbranch" ||
32 die
"git checkout: we do not like '$newbranch' as a branch name."
50 if rev=$
(git-rev-parse
--verify "$arg^0" 2>/dev
/null
)
52 if [ -z "$rev" ]; then
53 echo "unknown flag $arg"
58 if git-show-ref
--verify --quiet -- "refs/heads/$arg"
62 elif rev=$
(git-rev-parse
--verify "$arg^{tree}" 2>/dev
/null
)
64 # checking out selected paths from a tree-ish.
66 new_name
="$arg^{tree}"
84 case "$force$merge" in
86 die
"git checkout: -f and -m are incompatible"
89 # The behaviour of the command with and without explicit path
90 # parameters is quite different.
92 # Without paths, we are checking out everything in the work tree,
93 # possibly switching branches. This is the traditional behaviour.
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).
105 Did you intend to checkout '$@' which can not be resolved as commit?"
107 if test '' != "$newbranch$force$merge"
109 die
"git checkout: updating paths is incompatible with switching branches/forcing$hint"
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 $?
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
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.
131 git-rev-parse
--verify "$new^{commit}" >/dev
/null
2>&1 ||
132 die
"Cannot switch branch to a non-commit."
136 # We are switching branches and checking out trees, so
137 # we *NEED* to be at the toplevel.
140 [ -z "$new" ] && new
=$old && new_name
="$old_name"
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.
153 if test -z "$branch$newbranch" && test "$new" != "$old"
156 if test -n "$oldbranch"
158 detach_warn
="Note: you are not on ANY branch anymore.
159 If you want to create a new branch from this checkout, you may do so
160 (now or later) by using -b with the checkout command again. Example:
161 git checkout -b <new_branch_name>"
163 elif test -z "$oldbranch" && test -n "$branch"
168 git show-ref
-d -s |
grep "$old" >/dev
/null ||
{
170 "You are not on any branch and switching to branch '$new_name'
171 may 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>'.
175 Leaving your HEAD detached; not switching to branch '$new_name'."
183 echo >&2 "warning: You appear to be on a branch yet to be born."
184 echo >&2 "warning: Forcing checkout of $new_name."
190 git-read-tree
--reset -u $new
192 git-update-index
--refresh >/dev
/null
193 merge_error
=$
(git-read-tree
-m -u --exclude-per-directory=.gitignore
$old $new 2>&1) ||
(
196 echo >&2 "$merge_error"
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 ||
exit
205 eval GITHEAD_
$new=${new_name:-${branch:-$new}} &&
206 eval GITHEAD_
$work=local &&
207 export GITHEAD_
$new GITHEAD_
$work &&
208 git merge-recursive
$old -- $new $work
210 # Do not register the cleanly merged paths in the index yet.
211 # this is not a real merge before committing, but just carrying
212 # the working tree changes along.
213 unmerged
=`git ls-files -u`
214 git read-tree
--reset $new
219 z40
=0000000000000000000000000000000000000000
221 sed -e 's/^[0-7]* [0-9a-f]* /'"0 $z40 /"
223 ) | git update-index
--index-info
229 if test "$saved_err" = 0
231 test "$new" = "$old" || git diff-index
--name-status "$new"
237 # Switch the HEAD pointer to the new branch if we
238 # checked out a branch head, and remove any potential
239 # old MERGE_HEAD's (subsequent commits will clearly not
240 # be based on them, since we re-set the index)
242 if [ "$?" -eq 0 ]; then
243 if [ "$newbranch" ]; then
244 if [ "$newbranch_log" ]; then
245 mkdir
-p $
(dirname "$GIT_DIR/logs/refs/heads/$newbranch")
246 touch "$GIT_DIR/logs/refs/heads/$newbranch"
248 git-update-ref
-m "checkout: Created from $new_name" "refs/heads/$newbranch" $new ||
exit
253 GIT_DIR
="$GIT_DIR" git-symbolic-ref HEAD
"refs/heads/$branch"
254 elif test -n "$detached"
256 # NEEDSWORK: we would want a command to detach the HEAD
257 # atomically, instead of this handcrafted command sequence.
259 # git update-ref --detach HEAD $new
260 # or something like that...
262 echo "$detached" >"$GIT_DIR/HEAD.new" &&
263 mv "$GIT_DIR/HEAD.new" "$GIT_DIR/HEAD" ||
264 die
"Cannot detach HEAD"
265 if test -n "$detach_warn"
267 echo >&2 "$detach_warn"
270 rm -f "$GIT_DIR/MERGE_HEAD"