SVN command-line

Slik SVN

Basic SVN Commands

#Switches
--m "message text"
--username <username>

#Help
svn help
svn help <command>
#Example
svn help co

#check-out
svn co svn://[@rev]... [path] --username <username>

#check-in / commit - defaults to user who checked-out
svn ci [path...] -m "message text"

#Mime-type
svn propset <propname> <propval> <file path...>
#Examples
svn propset svn:mime-type text/plain <file path>
svn propset svn:eol-style native <file path>

#Add
svn add <dir/file path...>

#Copy - Branch/Tag
WC=Working Copy
WC path -> WC path (copy and sched for addition w/history)
WC path -> URL     (immediately commit copy of WC to URL)
URL     -> WC path (co and sched for addition)
URL     -> URL     (branch / tag)
svn cp [src path] [dst path] -m "message"

#Move
svn mv <src> <dest>

#Delete
svn delete <remote url... or local path...>

#update
svn up [path...]
svn up -r <revision>

#Statuses

''=None
A=Added
D=Deleted
M=Modified or properties modified
R=Scheduled for deletion and replaced in WC
U=Updated
C=Conflicted
G=Merged
X=present due to external definitions
I=Ignored
?=Not under version control
~=versioned as one type of object, but replaced as different type of object
L=Locked
S=Item is switched
K=File is locked in this WC
O=File is locked by another user in another WC
T=Locked in this WC, but lock has been stolen and is invalid
  Lock is in repository
  only appears with --show-updates
*=A newer revision exists on the server


#revert
svn revert [path...]

#cleanup - removes locks, finishes operations
svn cleanup [path...]

#Outstanding changes
svn status [path]

#Current user and revision
svn info

#Restore deleted branch
svn copy svn://host/projects/branches/someBranch@1234 svn://host/projects/branches -m "Restore branch from rev 1234."



Commit template:

svn propedit tsvn:logtemplate .

Set editor in Windows:

set EDITOR=notepad.exe


HowTo Revert trunk/head to older version or use tortoise and right click.

HOTO pull back revision to work on it locally:

For example. Revision 313

Create a patch file by doing the following:

C:\vn>svn diff -r 312:313 > r313.patch

Specify the previous revision up to the revision you want to create a patch for and save it to a file.

Right-click that patch file with TortoiseSVN and apply the patch to your local copy

Comments

Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will atte...
Read more

Locks held on Oracle for hours after sessions abnormally terminated by node failure

If a session holds db locks and is abnormally terminated (no fin/ack), the locks will persist until the db session is closed, typically around 2 hours and 12 minutes with default network tcp_keepalive settings. Abnormally terminated does not include CTRL C or kill -9. The ojdbc6 driver apparently has a shutdown hook thread that closes the connections in graceful shutdowns. The OS apparently closes the connections when processes are killed. Abnormally terminated might include power failure, firewall failures, Out Of Memory, OS/kernel crash, network connection failure, JBoss or other server node failure, etc. This was easily reproduced by creating a  process that connected to the db and updated a record but did not commit. While the first process was waiting, a second process with a contending update was started which blocked on the first update. The first clients network cable was then disconnected. The second clients transaction waited for approximately 2 hours until the databa...
Read more