What is the flow for svn update in this scenario? -


ok know command works, have silly question have not been able answer.

let's have svn repository file named a.txt, , has got number in x, user checks out , locally changes y in a.txt, wants commit it, before doing svn update, ideally should happen svn update should throw conflict because both of these files different. in case svn update runs , says no current changes between repository , working copy.,

can tell me reasoning correct? in opinion scenario similar standard svn conflict between 2 users

edit: looking @ answer of sharptooth, clear reasoning incorrect, can please provide flow overview of svn update? i.e.if have got r repo , w working copy, svn update while calculating diff?

your local working copy contains files in original state current revision. these original files stored in .svn folder. size of .svn folder in essence equal size of project files. when issue update svn client update .svn folder latest revision, , try update working files. if file changed try merge changes in working file. if cannot merge complain conflict. happens if both new revision , working file have changed same line in file. have resolve conflict, bearing in mind old, arrived new repository, , own changes.

once issue commit, svn client first checks if working copy has recent revision, , if has sends server differences between working files , files in .svn folder. if goes copies different working files .svn folder, , .svn folder in sync repository on server.


Comments

Popular posts from this blog

html - How to style widget with post count different than without post count -

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

javascript - storing input from prompt in array and displaying the array -