aboutsummaryrefslogtreecommitdiff
path: root/Documentation/howto/rebuild-from-update-hook.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-08-25 18:15:32 -0700
committerJunio C Hamano <junkio@cox.net>2005-08-26 22:06:17 -0700
commitb10ac50f1e9ef851128f9800cd481d8cace18f01 (patch)
treeb48c2fd1edb6d80609a94e2078b23034057e9a1e /Documentation/howto/rebuild-from-update-hook.txt
parent90bc118fc53916a623cad84e72b7dec597907b1e (diff)
downloadgit-b10ac50f1e9ef851128f9800cd481d8cace18f01.tar.gz
git-b10ac50f1e9ef851128f9800cd481d8cace18f01.tar.xz
Fix pulling into the same branch.
When the "git pull" command updates the branch head you are currently on, before doing anything else, first update your index file and the working tree contents to that of the new branch head. Otherwise, the later resolving steps would think your index file is attempting to revert the change between the original head commit and the updated head commit. It uses two-tree fast-forward form of "read-tree -m -u" to prevent losing whatever local changes you may have in the working tree to do this update. I think this would at least make things safer (a lot safer), and prevent mistakes. Also "git fetch" command is forbidden from fetching and fast forwarding the current branch head unless --update-head-ok flag is given. "git pull" passes the flag when it internally calls "git fetch". Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/howto/rebuild-from-update-hook.txt')
0 files changed, 0 insertions, 0 deletions