![]() So you get up-to-date and try again, but have a conflict: git add filename.c You're going to pull some changes, but oops, you're not up to date: git fetch originįrom ssh:// :22/projectnameĮrror: Entry 'filename.c' not uptodate. Here's a probable use-case, from the top: If you want to get changes from LOCAL :diffg LO If you want to get changes from BASE :diffg BA If you want to get changes from REMOTE :diffg RE You could edit the MERGED view the following way More info about vimdiff navigation here and here You can directly reach MERGED view using ctrl+ w followed by j. You can navigate among these views using ctrl+ w. MERGED – merge result, this is what gets saved in the repo REMOTE – file you are merging into your branch LOCAL – this is file from the current branchīASE – common ancestor, how file looked before both changes ![]() Step 3: You will see a vimdiff display in following format +-+ Step 2: Run following command in terminal git mergetool This will set vimdiff as the default merge tool. Step 1: Run following commands in your terminal git config merge.tool vimdiff Kdiff3, tkdiff, xxdiff, tortoisemerge, gvimdiff, diffuse,Įcmerge, p4merge, araxis, vimdiff, emerge.īelow is the sample procedure to use vimdiff for resolve merge conflicts. ![]() One of the following tools to use it instead: meld, opendiff, Running git mergetool for me resulted in vimdiff being used. ![]() It is much better than doing the whole thing by hand certainly.ĭoesn't necessarily open a GUI unless you install one. Sometimes it requires a bit of hand editing afterwards, but usually it's enough by itself. It opens a GUI that steps you through each conflict, and you get to choose how to merge. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |