I'm truckin along in my project and I had a "Hold my beer, I'm gonna try 
somthin'" moment and it did not work and the edits are all through the 
code. Generally I would Update to Revision and choose Rev 513 (the one 
before the event) and I go on my merry way, edit then commit which will 
generally just create the next highest build number with the newly edited 
working copy.

For some reason this SVN rookie does not understand, if I now Update to 
Revision 513, edit, then commit, the blasted thing is merging the bad code, 
Rev 522 with mine and putting all the <<<<<< mine <<<<<< rev522 crap in my 
code along with the code that doesn't work.

I want to make a clean break and hop over rev 522 and have a 523 revision 
Without the merging. I would be happy to delete all revisions from 514 to 
522 if I can to pull this off but I don't have much confidence going 
forward. For a year now VisualSVN and I have been the best of friends but 
now I don't like it so much. :-)

:Ron  

-- 
You received this message because you are subscribed to the Google Groups 
"VisualSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to visualsvn+unsubscr...@googlegroups.com.
To post to this group, send email to visualsvn@googlegroups.com.
Visit this group at http://groups.google.com/group/visualsvn.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to