Tutorial from Svn's Goddess

General todo before merge code
- svn ci -m 'message'

- svn log --stop-on-copy
from working branch for get revision number from to
- svn up
from trunk

- svn merge -r from:to
from trunk

-> if something conflict , there have some choice to
1.choose one is mine
2.choose others
3.postpone (leave conflict file there)
if choose 3 :
go to that file to remove unwanted line
- then >> svn resolved filename
- svn st
for check everything allright
- svn ci -m 'message'


(very thank air)

Comments

Post a Comment

Popular posts from this blog

Difference between apt-get update and apt-get dis-upgrade

The “sudo apt-get upgrade” isn’t necessary. It’s a different type of upgrade from “dist-upgrade” You either run one or the other. “apt-get upgrade” will only update your existing packages while “apt-get dist-upgrade” will update your existing packages, remove obsolete packages and install new available packages as well. You can get breakages either way since new packages might be required as dependencies for upgraded packages in the case of “sudo apt-get upgrade” so using “apt-get dist-upgrade” is still the best way so far. Note: This only applies to LMDE since LMDE is a true rolling release. For any other flavor of Mint you’d use MintUpdate levels 1, 2 and 3 all the way. Perhaps someday Clem and Co. will figure out how to tailor MintUpdate so it works properly in LMDE but considering the rolling aspect of LMDE, I’m at a loss as to how theyn would do that. ref http://b10gger.wordpress.com/2011/03/20/difference-between-apt-get-upgrade-and-apt-get-dist-upgrade/ (thank for this website)
Read more