Lets prepare that new repository so that it’ll support a trunk, branches and tags. However, to support these capabilities we’ll need to prepare a new repository first. These concepts of Tagging and Branching are explained in detail below.
#Tortoisesvn does not copy log when branch code
Thinking ahead though you will want, at some point in the future, to combine this new prototype code with your existing working code. What you need is a new copy of the files in your repository that you can make changes to without affecting the existing repository.
However, you don’t want to contaminate your existing repository (with all the working code) with a new prototype code that won’t work for some time. Your team wants to work together and collaborate on this so you want to continue using SVN for this new work. You and your team think pulling together a prototype version for this functionality would be a great idea. They’ve been released into a production environment and nobody wants to risk changing anything just in case you break something.Īlong comes your end user who says wouldn’t it be great if we could add some functionality to support X, Y, and Z. Say you have a set of files in your repository that is working perfectly. So we can use SVN’s tagging feature and tag that same revision with the tag v1.2 Far easier to remember and in line with the version number we could be using when we release our software.īranching is one of the core features in SVN that allows us to work on a different instance of the files the files that are contained in the repository. So you’re likely to get to the point where you have a stable set of files that you know are in good shape and the SVN revision number might be r2343. In a reasonably sized project, over a year or two, it’s not long before those revision numbers get into the thousands or even tens of thousands. Branching gives us the capability to create a copy of the folders/files in our repository and have a different copy to work on – without fear of corrupting our main copy.Īs you’ve probably already grasped every time you commit a changed file to the repository SVN gives the repository a new, incremented by 1, revision number. Tags allow us to give a more human-friendly name to a specific revision of our folders/files.
#Tortoisesvn does not copy log when branch how to
The TortoiseSVN manual is quite explicit in how to do this. If you wanted to make a new branch completely on the server, just use: svn copy svn:///repo/trunk/ svn:///repo/branches/1.4Ĭan you list the steps needed to branch from a directory? Subversion is really just a set of command-line tools, and TSVN is a wrapper around them. The TortoiseSVN GUI doesn't represent the complete set of operations that is possible with Subversion. Why cant we branch from Repository GUI itself, (would be head revision) ? Update: The OP added some additional questions that weren't part of the original, so I've amended my answer. some other arbitrary revision (specific revision).where the repository is currently at right now (repository's HEAD revision).where you're working from right now (your working copy revision).
TSVN is asking you what you would like that point to be, and you have one of three choices: When you branch, you're being asked to branch from a specific point. Since people may have committed things while you're working, your working copy revision may not necessarily equal the HEAD revision. Your working copy revision is the revision reflected by the current tree you have.
The head revision in the repository is the most recent revision that has been committed to source control.
0 kommentar(er)
