Tortoisegit updating to revision sql updating identity column
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 184.108.40.206 git version 220.127.116.11.1367.gcd48 running on xp sp3 Please provide any additional information below.Every project on Git Hub comes with a version-controlled wiki to give your documentation the high level of care it deserves.It’s easy to create well-maintained, Markdown or rich text documentation alongside your code.Sign up for free See pricing for teams and enterprises Tortoise Git provides a GUI extension for Git, within Windows, and installs itself within the Windows File Explorer.This allows Windows File Explorer to access a Git repository.
All commits that came after this version are effectively undone; your project is exactly as it was at that point in time.
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.
As the makers of Tower, the best Git client for Mac and Windows, we help over 100,000 users in companies like Apple, Google, Amazon, Twitter, and Ebay get the most out of Git.
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.
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?