When does svn BASE become equal to the HEAD--- "svn log -rHEAD:1"

 

链接：http://stackoverflow.com/questions/742772/when-does-svn-base-become-equal-to-the-headWhen does svn BASE become equal to the HEAD

Project Tongtong (currently pre-launch/stealth) - Founding Engineer New York, NY; Shanghai, China

GameChanger Media, Inc. - Mobile App Software Engineer New York, NY

LinkShare Corporation - Senior Software Engineer Tampa, FL

Spruce Media, Inc. - Social Web Developer - Facebook API San Francisco, CA; Washington, DC

up vote 4 down vote favorite 4 share [fb] share [tw]

I had a question regarding the BASE version in svn. I know it is the pristine version of an item from the last time update was run and svn diff and status basically run against this version. When does the BASE get updated? Does it get updated to the HEAD when update is run? Is this always true even if there was a conflict during update? What does BASE have incase of a conflict? Does it still have the version from my last update(before the most recent update that caused a conflict) or will it be updated to the HEAD even if there is a conflict? Also when svn commit is run I am assuming the BASE gets updated with my local changes and at this point BASE, HEAD and my local copy all are the same? Provided the commit was successful. svn link | improve this question edited Apr 13 '09 at 1:24 asked Apr 13 '09 at 1:17 HeretoLearn 320 1 3 14 57% accept rate

feedback

4 Answers

active oldest votes

up vote 12 down vote accepted

HEAD is the latest revision in the repository. BASE is the last revision you have obtained from the repository. They are the same after a successful commit or update. When you make changes, your files differ from the BASE copies. When you revert, they go back to matching the BASE revision. When you get a conflict, you do not update the repository. Rather, your files are considered to still be "being edited" as if you were making changes. After you resolve conflicts, you have in essence decided what the final files will look like and you then commit them as you would have normally. So, conflicts are like a case of special editing. link | improve this answer answered Apr 13 '09 at 7:14 gbarry 1,831 4 11 21

2   They are the same, however briefly, after an update, though not necessarily after a commit. Consider directories and "mixed revision working copies". –  bendin Apr 14 '09 at 9:13   Apparently creating these "mixed revision working copies" -- which means you can create a commit without complete knowledge of what's going on -- is a consequence of one of the "fundamental rules of Subversion". –  Josh Lee Oct 14 '09 at 10:07 feedback

up vote 2 down vote	It matters when you are viewing logs, because svn log without url shows your BASE log, but with url your HEAD log, that's why i always use "svn log -rHEAD:1" to see all the changes. link | improve this answer answered Oct 14 '09 at 8:44 codein 21 1
	feedback

up vote 2 down vote

BASE is the revision of your working copy as it exists in the repository. In other words, your revision without the changes you've made. So if you svn update a file or folder to HEAD, then BASE and HEAD are equal. When there is a conflict, BASE becomes the revision before the commit that conflicted with your working copy. Run svn info on an item to see it's BASE revision. Revision Specifiers link | improve this answer edited Feb 24 '10 at 22:30 keparo 6,449 2 28 47 answered Apr 13 '09 at 6:20 sirlancelot 2,281 2 6 29

feedback

up vote 0 down vote

Theory: After a successfull recursive update or switch the base version of all your files becomes head. After a commit or partial update some files might be at the HEAD revision, but only after an update that didn't skip files you can be sure that all files are at the same version. (Reasons for skipping are unversioned obstructions or conflicts). But, why would you need to know this. Subversion should know this internally, but this knowledge shouldn't really matter to the user in most cases. (Subversion automatically warns you when files are out of date). As far as I can tell, the only time you really need to make sure that you are at a stable version is, when you are creating a branch from a working copy. link | improve this answer edited Apr 14 '09 at 9:03 answered Apr 13 '09 at 20:26 Bert Huijben 7,306 1 13 26

1   I just wanted to figure out how svn works and its implementation details. Thanks for your response. –  HeretoLearn Apr 14 '09 at 2:04