Please note that other Pearson websites and online products and services have their own separate privacy policies. This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site.
Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site. $ svn switch file:///home/bill/my_repository/trunk/Īs you can see, Subversion updates your hello.c file so that it represents the trunk version, rather than your modified branch version of the file. If you don't make the switch as soon as you're done with the branch, it can be all too easy to forget and accidentally apply modifications to the wrong place. Of course, now that you're done modifying the branch, it's a good idea to switch your working copy back to the trunk. $ svn log file:///home/bill/my_repository/trunk/hello.c R1 | bill | 16:28:57 -0500 (Thu, ) | 1 lineīut the the original hello.c file, still only shows the first two revisions. R4 | bill | 22:47:11 -0500 (Mon, ) | 1 lineĬreated a branch of the project to make the boss happy $ svn log file:///home/bill/my_repository/branches/cvs_version/hello.c $ svn commit -message "Changed program output to praise CVS"Īfter the commit, the branch shows the committed change. Then, when you commit those changes, they will be applied to the copied version of the file, but the original file will remain unaffected, as you can see in the log outputs here. Printf(" CVS is the best!!\n") // Ugh! The boss made me do it For instance, to make your boss happy, you might change my_repository/branches/cvs_version/hello.c to look like this: Now that you have switched your working copy to point to the branch, you'd probably like to make some changes to the branch. URL: file:///home/bill/my_repository/branches/cvs_version For instance, the following command line will show you that your current working copy is switched to the cvs_version branch (look at the URL line). You can look at what directory you are currently switched to by running svn info.
Had they been different, Subversion would have updated all of your working copy files to reflect the cvs_version/ directory that you switched to. In this particular case, running svn switch didn't make any changes to the files in your working copy, because the branch and your trunk are identical. The files in your working copy now point to the branches/cvs_version/ directory, and any changes that you commit will be applied to that directory. $ svn switch file:///home/bill/my_repository/branches/cvs_version To switch your working copy to the branch, run the following command line. To do this, you need to use the svn switch command. Instead of checking out a new working copy, you can switch your current working copy to point to the branch, instead of the /trunk directory that it points to now.
You could check out the branch (using svn checkout) into a new working copy. $ svn copy -message "Created a branch of the project to make the boss happy" file:///home/bill/my_repository/trunk/ file:///home/bill/my_repository/branches/cvs_versionĪfter you have created the branch, you'll need to put it into a working copy so that you can make changes to it. Therefore, you make them exactly the same way only in this case, you will want to copy the files into the branches directory, instead of the tags directory. The solution is to create a branch of the project, which will allow you to take the project in a different direction, while maintaining the current development path in parallel.īranches in Subversion are just like tags, copies of the original repository part they refer to. Because you know he's heading down a dead-end path, though, you don't want to stop development on your already excellent version of Hello World. Say, for example, that your boss isn't yet quite as enlightened as you are, and decides you need to release a version of Hello World that touts that other version control system. You should have tags pretty well down at this point, so let's take a look at branches. Subversion Version Control: Using the Subversion Version Control System in Development Projects
0 kommentar(er)
