This is the continues tutorial for svn command line tutorial for beginners 1. The previous post covers Introduction of subversion, installation links, how to get help, create svn repository, import files into a new repository and list the files inside a repo.
svn command line tutorial for beginners continues ….
How to checkout files from svn repo?
This is the most critical part of svn and also the most common part of svn command line. A lots of open source development projects provided the way for user to check out their latest code through the internet.
You need to check out in order to commit the changes to svn repo later. Refers back to the previous post, where I import entire directory /home/mysurface/programming to programming_repo. I am going to checkout to the same folder. If you are skeptical of doing this, you may want to backup the directory first.
mv programming programming-bk
Now checkout to programming, mkdir is not needed, as svn will create the directory for you if it is doesn’t exist.
svn co file:///home/mysurface/repo/programming_repo programming
co is the shortform of checkout.
Okay, lets just compare both folder with diff and store the result into a file comp.diff
diff programming programming-bk > comp.diff
Diff will list the folder in common, and also the differences. Check comp.diff, as it tracks the additional folder .svn that only exist in programming/. Again, do NOT modified or delete this folder.
Are you convinced to remove your programming-bk/ ? Make sure you keep the repo safe and you can check out the same data anytime, at any place.
You can even checkout only a specific file or specific folder from your repo. e.g.
svn co file:///home/mysurface/repo/programming_repo/c/curses/matrix.cc This will only check out a file at current directory.
Single file can’t be checkout like directories, but you can extract them from repository by svn export
svn export file:///home/mysurface/repo/programming_repo/c/curses/matrix.cc
How to track the changes before commit to repo?
First of all, you track what files had changed,
It will list files which have changed, with some attributes besides the filename. Common attributes are M, ?, A … M is modified, A is newly added (how to add refers later section), ? indicate the file is added into local directory but not added into repo.
Secondly, you want to track the differences between the previous revision and the working one. Lets assume color.c has changed,
svn diff color.c
I really don’t like svn diff ‘s result. Fortunately, I found a simple bash script what makes vimdiff as the compare tool. The script was written by Erik C. Thauvin, you can get it from here.
I name it as svndiff and place it at /usr/bin, change the mode to executable.
chmod +x /usr/bin/svndiff
Now, I can simply do this,
To close the vimdiff, type
How to commit the changes?
You can commit with -m to place your log message if it is short. But if it is long, I suggest you to make use of your default editor. I am a vim user, therefore I add a line into my ~/.bashrc
Now I can commit with this:
ci is the shortform of commit. Write the log message and close save vim
:x, I am done. The same way as checkout, you can choose to commit one file or any folder.
How to add or delete file to or from repo?
The file won’t be committed if you don’t add it into repo. Therefore you need to add it manually if you want it to goes into your repo. Let say you wanna add a new file color2.cc
svn add color2.cc
Delete does the same way, if you only delete file at your working directory, it won’t reflects the changes to our repo.
How to check the logs for each revision?
The simplest way is doing just,
It will list all logs, start from latest revision. That is really irritating! You can limit it to 3 latest revision log by doing this
svn log --limit 3
If you wanna check for specific revision, specified with -r,
svn log -r 3
I find something awkward, let say I have done svn delete at revision 3 (latest), and revision 2 is the changes of the deleted file at revision 3. When I do
svn log, by right it should show all 3 logs, but It only shows for revision 1. It means the svn log will only shows the log if the file is exist, bare in mind.
How to update the working directory into the latest revision?
Update to specific revision?
svn update -r 3
I think thats all for normal use of svn commands, further reading at http://svnbook.red-bean.com/.
[tags]svn tutorial, subversion, svn howto, source version control[/tags]