Операция | Official client | TortoiseSVN |
---|---|---|
checkout
(create new working copy) (*) |
svn checkout https://svn.local/svn/test/trunk
(svn co [URL]) |
|
update
(update working copy) (*) |
svn update (svn up) |
|
commit
(save changes to repository) (*) |
svn commit (svn ci) |
|
stat
(examine working copy status) (*) |
svn status (svn st) |
|
diff
(review changes) |
svn diff (svn di) |
|
switch
(WC to new repository URL) (*) |
svn switch [новый URL] (svn sw) |
|
add
(add file/directory to working copy) |
svn add [file/dir] |
|
remove
(remove file/dir from WC) (*) |
svn remove [file/dir] (delete, del, remove, rm) |
|
copy
(to create branch/tag, for example) (*) |
svn copy [URL1] [URL2] (svn cp)
svn copy \ https://svn.local/svn/test/trunk \ https://svn.local/svn/test/branches/private_vnaum |
|
revert
(local changes) |
svn revert |
|
log
(view changelog) |
svn log |
|
merge
(apply changeset from repository to WC) (*) |
svn merge -r N:M SOURCE[@REV] |
To merge revisions you need to go to a working copy of the branch in which you want to receive the changes, often the trunk. Select Merge... from the context menu.
|
Grab it from http://subversion.tigris.org/files/documents/15/35379/svn-1.4.2-setup.exe .
Perfectly documented in Version Control with Subversion. Works on any OS out there. This client will be installed on development and production boxes. Has built-in help for every command (for "svn checkout" - "svn help checkout", and so on).
I strongly recommend this client for starters.
Grab it here:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.1.7992-win32-svn-1.4.2.msi?download
Popular client for Windows.
Implemented as a windows shell extension (you will need to click with
right mouse button on everything).
Pretty good help file in chm format.
With excerpts from The Great Book
(Version Control with Subversion).
You can checkout any directory / branch from repository.
You can even checkout whole repository (like that: svn co
https://svn.local/svn/test/), but beware - "cheap copies" are only cheap in
repository, not on your hard drive! And if single branch takes 100Mb, 10
branches will take 1Gb.
update, like almost every operation in SVN, works on current dir recursively.
And, like almost every operation, you can explicitly tell it what (and how) you want to
update:svn up -r 10 file - update file file to revision 10. You can update to any past revision.
By default it commits current dir recursively.
You can explicitly tell what you're going to commit.
Before committing you'd better once again review your changes with svn
diff, it will help you to write better commit message.
This is how I do my commits:
svn diff | gview - ; svn ci
There are a lot of letters in stat output.
Most popular are M - modified file, A - added file, D - deleted file.
Full legend is available here:
http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.examine.status
Always check output of this operation.
If switch fails, you can by mistake commit your changes on wrong branch.
This operation can be done server-side - just put an URL in repository instead
of WC path.
This operation can be done on WC, too - just put a WC path instead
of URL in repository.
Check Starters Guide.
TortoiseSVN
Footnotes:
checkout:
update:
commit:
stat:
switch:
remove:
copy:
merge: