While doing a git svn rebase, if you have merge conflicts here are some things to remember: 1) If anything bad happens while performing a rebase you will end up on a (no-branch) branch. 2) If you run git status, you’ll see a .dotest file in your working directory. This is safe to ignore. 3) … Read more
Skipped obstructing working copy this means that there’s a working copy folder in the way: your update wants to add a folder with name ‘project’, but you already have a versioned folder ‘project’ in your working copy. Maybe you moved that folder from another working copy? Or that folder is its own working copy (if … Read more
You don’t need mergetool for this. It can be resolved pretty easily manually. Your conflict is that your local commits added a file, vision_problem_8.h, that a remote commit also created, by a rename from vignette_generator_mashed.h. If you run ls -l vision_problem_8.h* you will probably see multiple versions of this file that git has preserved for … Read more
Add -X ours argument to your git merge command. Say you are working in your local branch. Then you want to merge in what went in the master: git merge -X ours master On the other hand if you are in master and want to merge your local branch into master then @elhadi rightly says … Read more
I have solved the same problem by using the Git command prompt in Visual Studio, because it gives you more ability: http://msdn.microsoft.com/en-us/library/vstudio/dd286572.aspx You also may install this extension to facilitate the work with it (it gives you ability do not enter passwords each time): http://gitcredentialstore.codeplex.com/ Then I used this commands: git pull // I got … Read more
Per the docs, I just tried this simple command and it worked for me: git commit –no-edit Afterward, run git log to confirm that the default message has been used.
If you really want a copy of HEAD (the latest revision in repos), then you should svn revert -R <path> // discard all your changes inside path (recursive) svn update // get latest revision of all files (recursive) That’s it. Beware that you will lose ALL your changes since your last ‘commit’. EDIT: added the … Read more
You have probably already noticed that the order of loading the packages makes a difference, i.e. the package that gets loaded last will mask the functions in packages loaded earlier. To specify the package that you want to use, the syntax is: chron::is.weekend() tseries::is.weekend() In other words, use packagename::functionname() In addition, if you know that … Read more
I use git but we see the same issue – if two people add files there’s a merge conflict. Usually the editing is very easy though. Simply go into the project.pbxproj file with a text editor, and look for the merge conflict section – usually this is marked by something like : >>>>>>> Stuff 1 … Read more
Option 5, a custom merge driver, is probably the way to get closest to what you want. It is surprisingly easy to do. Below is an example of one that I think should get you pretty close to the behavior you desire. First, create a merge driver script called merge-and-verify-driver. Make it executable and put … Read more