SVN Commands Cheat Sheet

SVN commands allow you to work more efficiently in Subversion.

Example: How to Display List of SVN Repositories

For example, using SVN commands can help you display a list of SVN repositories. Simply use the svn list repository command, and you’ll get a list of all repositories and their contents.

Of course, this is just one of many useful SVN commands you should know.

Switching From SVN? Get a Better Tool

Many teams have switched from SVN to Helix Core. That’s because Helix Core delivers greater speed, scale, and security. Because the commands are similar, it’s easy to get started. Get it free for up to 5 users.

Basic SVN Commands

Here are the basic SVN commands that every developer and admin should know.

svn admincreate

The svn admincreate command creates a new, empty repository.

svn import

The svn import command commits an unversioned tree of files into a repository (and creates intermediate directories, if needed).

svn checkout

The svn checkout command checks out a working copy from the repository. This command is sometimes shortened to svn co.

svn commit

The svn commit command sends your changes back to the SVN server.

svn add

The svn add command will add a new file to the repository — but only after you’ve done a svn commit.

svn delete

The svn delete command will delete a file from your working copy of the repository.

svn list

The svn list command allows you to see a list of files in a repository without creating a working copy.

svn diff

The svn diff command reveals the differences between your working copy and the copy in the master SVN repository.

svn status

The svn status command prints the status of working copy files and directories.

svn info

The svn info command displays information about a local or remote item.

svn log

The svn log command shows log messages from the repository.

svn move

The svn move command moves a file from one directory to another (or renames it).

svn merge

The svn merge command combines two different versions into your working copy.

svn revert

The svn revert command reverts changes in your working copy, as well as property changes. For example, you can use svn revert to undo svn add.

svn update

The svn update command updates your working copy with changes from the repository.

svn shelve

The svn shelve command stores your changes without submitting them.

svn help

The svn help command provides a summary of available commands.

SVN Commands Cheat Sheet

Need a handy SVN commands cheat sheet to reference?

Here, we’ve compiled a quick reference guide to every SVN command you’ll need to know. We’ve also included the Helix Core P4 command equivalent, if you’re considering migrating to Helix Core.

SVN Commands Cheat Sheet

Task	SVN Commands	Helix Core P4 Commands
Create a new depot/repo.	svnadmin create	p4 depot
Add files to the depot/repo.	svn import	p4 reconcile, then p4 submit
Discard changes made to open files and revert back to latest synced version.	svn checkout -r url://path/to/repo	p4 revert
Copy files into the client workspace.	svn checkout	p4 sync, then p4 edit
Send changes to the depot.	svn commit	p4 submit
Open files in a client workspace to add them to the depot.	svn add , then svn commit	p4 add , then p4 submit
Remove a file.	svn delete	p4 delete
Obtain list of files in a repository.	svn list	p4 files
Compare files on the client workspace with revisions in the depot.	svn diff	p4 diff
Display information about the workspace files.	svn status	p4 fstat, p4 opened, p4 have, p4 files
Display information about the current client and server.	svn info	p4 info
Provide information on changelists and changelists’ files.	svn log	p4 describe
Move a file.	svn move	p4 move
Combine two different revisions.	svn merge	p4 merge
Discard changes made to an open file.	svn revert	p4 revert
Obtain and update changes from the depot/repo to the client workspace.	svn update	p4 sync
Store files without submitting.	svn shelve	p4 shelve
Request help.	svn help	p4 help

Switch From SVN Commands to P4 Commands

Helix Core and SVN can both handle large files better than Git. And they do have many basic, similar commands. But this is where the similarities end.

Find out why SVN teams are migrating to Helix Core — and why your team should, too.

Записки программиста

Краткая шпаргалка по основным командам Subversion

15 февраля 2016

Не могу сказать, что я большой фанат Subversion. По-моему, Git прекрасен, и никакие другие системы контроля версий не нужны. Тем не менее, работать с Subversion время от времени приходится, потому что нужно сделать checkout какого-то древнего полумертвого проекта или еще почему-то. Так что, в этой заметке мы рассмотрим основы работы с Subversion, ну и заодно почему он иногда может быть даже интереснее, чем Git. Заметка рассчитана на тех, кто уже имеет опыт использования Git или хотя бы Mercurial.

Перекрестная ссылка: Вас также может заинтересовать старенькая заметка Мой первый опыт работы с Subversion. Там речь идет больше про настройку серверной стороны, а также про использование всяких TortoiseSVN и прочих GUI. Данный же пост посвящен работе с уже существующими репозиториями из консоли.

Итак, почему же Subversion иногда может быть интереснее, чем Git:

• Считается, что централизованную систему контроля версий проще объяснить новичкам;
• Используются последовательные номера ревизий, ясно что за чем шло;
• Тут можно чекаутить отдельные каталоги и делать для них свои бранчи;
• Есть поддержка file lock, что иногда, пожалуй, может быть удобно;
• Subversion лучше работает с бинарными файлами и компактно хранит их дифы;

Я, впрочем, не гугу Subversion. Но в первом приближении, вроде, все верно.

HOW-TO: шпаргалка по командам SVN

Первым делом — checkout:

Скачиваем последние изменения:

Проверяем ветку и сервер:

Для просмотра истории изменений:

Та же история, но с diff (аналогично гитовскому git log -p):

Узнаем, кто, когда, какие строки менял:

Смотрим незакоммиченные изменения:

Какие файлы были добавлены или изменены:

Смотрим изменения в рамках ревизии, аналогично git show в Git:

для просмотра комментариев:

для просмотра изменений:

Смотрим измененные в ревизии файлы:

Изменения по сравнению с текущей ревизией, аналог git diff:

Применение сохраненного в файл diff, аналог git apply:

Отменить последние изменения, аналог git reset —hard HEAD:

Показать текущее состояние репозитория:

Получить список бранчей:

Создаем новый бранч или тег:

Блокируем или освобождаем файл, чтобы его не могли изменять:

Также советую заглянуть по этой ссылке и скопировать себе еще одну шпаргалку по командам. А тем, кто планирует работать с SVN много и часто, рекомендую книгу об этой системе. На русский она переведена лишь частично, но разобраться несложно.

Алексей Zemond Панкратов

Check Also

Занимательная форензика. Извлекаем пароль из дампа памяти с помощью Volatility и GIMP

Задачи на форензику (криминалистику) в соревнованиях Capture The Flag делятся на несколько…

X-Tools #227. Подборка хак-тулз для ресерчера и пентестера

Смертельный коммит. Выполняем произвольный код в клиенте git

Инструментарий Android-разработчика. Подбираем программы, которые помогут в работе

Хранить вечно. Разбираем и эксплуатируем ошибку в интерпретаторе PHP

Ядовитая гифка. Эксплуатируем уязвимость в расширении gd для PHP

Meltdown и Spectre. Разбираем фундаментальные уязвимости в процессорах

Строим свой GitHub. HOW-TO по настройке GitLab, опенсорсной альтернативы Гитхабу

10 трюков с Dropbox

HOW-TO: Четыре не самых известных редактора кода для разработчиков

По следам хакера. Разбираемся со взломом сайта на WordPress

KDE на прокачку. 12 твиков, которые превратят «Кеды» в идеальный десктоп

Прокачай терминал! Полезные трюки, которые сделают тебя гуру консоли

1 комментарий

slinkin

| svn status
Это не «показать текущее состояние репозитория», а как раз таки показать список изменений в локальной копии.
Например вы сделали чекаут, внесли изменения в файлы, создали новые или удалили ненужные и уже готовы к коммиту — делаем svn status и смотрим список измененных файлов, удаленных (svn remove), добавленных (svn add) или «неопознанных» (создали через touch или в оконном менеджере, но не добавили их черезз svn add).

Svn commands in windows

The aim of this tutorial is to guide beginners for using svn command line with simple examples.

This post is not going to focus on svn installation, as the installation is available anywhere, let me list some links for you in case you are actually looking for installation.

Subversion Installation References

Installing Subversion (svn) on Linux (Debian Stable) Setting up Subversion and websvn on Debian How To Configure Web Access To Subversion Repositories Using Apache Install SVN with Web Access on Ubuntu

Part 1

How to get help with svn?

If you are looking for svn reference in man pages, you have gone to the wrong place. To check the references of svn commands, simple do this:

This will make svn list all the available functions, to get the function reference, let say checkout

The same thing goes to other svn related commands, such as svnadmin

How to create a svn repository?

First of all what is repository? It is a core file for svn, or you can call it a centralized svn backup database. After created it, it is just a directory with its files. IMPORTANT! Do NOT try to modify or add something into the repository, unless you know what are you doing.

To create a svn repo, let say I wanna create a repo to store all my programming codes, I do this

Remember try to use absolute path for everything, sometimes the relative path is not going to work.

How to import my existing directories into the new repo?

-m stand for log message, the first revision was created with log as «Initial import». You need to specified URL for the repo, URL is the standard argument for svn. Therefore for local file, you need to specified with file://

How to see what is inside the repo?

Another way of listing all the files and folder in the tree view, I use svnlook

The difference between svn list and svnlook tree is one expect URL another one do not.

Part 2

Part 2 will covers how to checkout, track changes, commit, add or delete files and message logs.

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.

Now checkout to programming, mkdir is not needed, as svn will create the directory for you if it is doesn’t exist.

co is the shortform of checkout.

Okay, lets just compare both folder with diff and store the result into a file 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 folder from your repo. e.g.

This will only check out a folder at current directory.

Single file can’t be checkout like directories, but you can extract them from repository by svn export

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,

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. http://vc.thauvin.net/svn/linux/svndiff/svndiff.sh?view=markup

I name it as svndiff and place it at /usr/bin, change the mode to executable.

Now, I can simply do this,

To close the vimdiff, type :qa

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

Now I can commit with this:

ci is the shortform of checkin as in «check in», or commit. Write the log message and close save vim 😡 , 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

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

If you wanna check for specific revision, specified with -r,

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, bear in mind.

How to update the working directory into the latest revision?

Update to specific revision?

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