When I did svn update
and SVN asked me about a few differences, I told it to postpone them.
Now I would like to resolve them, but svn update
just tells me "up to date", even though svn diff
shows me the differences.
How do I make svn update
ask me about the conflicts again?
To resolve a conflict do one of three things: Merge the conflicted text by hand (by examining and editing the conflict markers within the file). Copy one of the temporary files on top of the working file. Run svn revert FILENAME to throw away all of the local changes.
Step 1: View Conflicts Select: (p) postpone, (df) diff-full, (e) edit, (mc) mine-conflict, (tc) theirs-conflict, (s) show all options: Subversion is complaining that there is a conflict with the README file, and Subversion does not know how to solve this. So Jerry chooses the df option to review the conflict.
svn update
won't ask about the conflicts again because it has dealt with them.
As for the meaning of svn status
, The ?
files are not managed by SVN, the M
ones have been modified, and the C
ones are the conflicted ones that you postponed. If you open one of the C
files, and look through it you will see markers in your code showing you where the conflicts are. You need to edit each one of these, fix the conflicts and remove the markers. And then you need to run svn resolve
to tell SVN that things are OK. Make sure to use the --help
option and Google to learn how svn resolve
works before you run it.
If you don't do all of this, svn commit
will no longer work.
svn status
is really important to understand, because svn diff only shows things that happened locally after svn update
. But, svn status -u
gives an overview after querying the repository. Most importantly, it clearly identifies files with conflicts (C
in column 1) which you have to open in an editor and check manually.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With