Tortoisegit updating to revision Sexkamera xxx live sex girls cams kenia

20 minutes as it seemingly runs through every file in the repo. on February 22, 2012 (imported from Google Code)* --- What steps will reproduce the problem? This seem to have just started after updating to tortoisegit 1.7.7.0 git version 1.6.5.1.1367.gcd48 running on xp sp3 Please provide any additional information below.*By Frithu\.\.\. Voilà: you now have a new branch named "old-project-state" reflecting the old version of your project - without touching or even removing any other commits or branches.

I have uploaded a setup script to prepare the repo to demonstrate this. on February 05, 2013 (imported from Google Code)* --- What steps will reproduce the problem?Create a new revision on that branch with an updated submodlue cd submodule/ git checkout submod_second cd .. On master create a conflict with the file change (nothing to do with the submodule) git checkout master \#bring the submodule back to the revision it should be in master git submodule update \#create a conflict with the file only echo oldfile > git commit -am "updating file" 4.Attempt a rebase from local_second git checkout local_second git submodule update \#At this point, we are on the local_second branch with no local changes (submodule and files are up to date) \#TGIT: show log \#TGIT: change branch in log window to master \#TGIT: right click the 'master' label and click on 'rebase "local_second" on to this' \#TGIT: click start rebase What is the expected output? Once the rebase has started, a conflict will show in file.txt, but the submodule will show as modified as well. I expect a fast commit and instead am seeing " Preparing commit..." dialog with " Updating index" and taking > 20 minutes as it seemingly runs through every file in the repo. This seem to have just started after updating to tortoisegit 1.7.7.0 git version 1.6.5.1.1367.gcd48 running on xp sp3 Please provide any additional information below.