| Posted by rangy, 12-17-2010, 09:25 PM | | Hi,
I'm new to svn and I was hoping that someone could help me with these questions.
1. I've noticed in my logs that sometimes revision numbers jump around. Looking at my recent logs, I have a version 12, and then it jumps to 25. And then it goes 26, 27, etc. Why is that? In between commits I've added branches etc.
2. Using SmartSVN, when I go to create a branch, it asks me about "external revisions". What are external revisions?
3. In order to store "snapshots" I'm using tags and because I'm new to svn, I'm "afraid" to not have a hard copy of these snapshots on my local machine. Is the proper way to make a local copy simply to create the tag, and then check out a working copy of that tag? And then disassociate the folder from svn?
Thank you very much in advance!
|
| Posted by Krishopper, 12-18-2010, 12:02 PM | | 1 - The entire subversion folder uses a single revision scheme. So if you make a change in a branch, the next number goes to that change. If you go into a branch and check the logs, you will probably see those missing version numbers within there.
2 - See http://svnbook.red-bean.com/en/1.0/ch07s03.html
3 - Yes, a tag is a proper way to make a "snapshot". But I don't get why you would have to disassociate the folder from SVN? If you want a local copy on your machine, you can just check out a working copy of a tag and leave it at that. I don't see why you would need to disassociate it from SVN?
|
| Posted by rangy, 12-18-2010, 01:26 PM | | Thanks for the help. I want to disassociate it because I will often upload the tagged versions as a working website, and I don't want the .svn files included. For now I also still want to have "free" hard copies -- in my curent/old system I have this:
/client/website
/client/backups/websiteBackup_v1
/client/backups/websiteBackup_v2
....
so I like the flexibility of going back if needed. I KNOW svn does this too, but I'm just afraid of leaving it all on the server for now. And while I know I can go back to a previous version with svn, I've never "gone back" yet and I want to keep my old way in place until I test out reverting with svn.
|
| Posted by Krishopper, 12-18-2010, 01:33 PM | | Are you using the simple "svn" command line utility, or are you using something else to manage your svn work?
It's very very very easy to go to different revisions (backups) with SVN. I'd highly recommend trying it out and getting comfortable with it as soon as you can, and save yourself the extra work. I wouldn't worry about the ".svn" directories being part of your clients website directories. You can easily set up a .htaccess file to reject HTTP access to those.
It will also allow you to jump back to older backups (versions, is the right terminology) much faster, since it only needs to update files that have changed, it doesn't need to copy everything over (unless you're doing an initial checkout).
|
| Posted by rangy, 12-18-2010, 01:43 PM | | I have to get used to the idea of only rolling back the file(s) that have changed. It's going to take a leap of faith for me to not have a full-directory hard copy of each version. But I'll try....
|
| Posted by Krishopper, 12-18-2010, 01:52 PM | | Just curious - have you had a look at any tutorials/books on SVN? to where they describe that SVN is really just a bunch of directories? Each tag or branch is just another directory with a copy of all of your files from where you made the tag or branch from. but the backend of SVN is smart so that it doesn't physically make a whole copy when you create a tag/branch and waste space on all of the duplicate files?
Last edited by Krishopper; 12-18-2010 at 01:57 PM.
|
| Posted by rangy, 12-18-2010, 10:32 PM | | Yes, I've browsed the SVN manual. I understand that SVN doesn't really copy everything, and that it basically a very "smart" system that records things in time, so that if I need to go back in time, svn can reconstruct.
I know that -- but again -- coming from YEARS of working with full hard copies of every version, it's going to take some time for be to be comfortable.
|
|
 Add to Favourites
 Print this Article
|
