[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn Checkout Works Like svn Update when working copy already exists?

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2005-04-29 22:07:37 CEST


I've found that when 'svn checkout' is run on a pre-existing working
copy it acts just like 'svn update'[1]. My checking of --help,
googling, and svnbook perusal all could not find any information about this.

Is this documented somewhere? Is there any difference between a
checkout on a pre-existing WC and an update, besides the fact that
checkout requires an explicit URL? (The reason I care is that if this
is proper, supported behaviour then in the context of our ant scripts
only one simple "checkout" target is needed which will either checkout
or update, depending on the state of the build tree.)

Thanks for any pointers,


svn, version 1.2.0 (Release Candidate 2)
    compiled Apr 22 2005, 08:25:36

# check out working copy 1
svn co svn://server/testrepo/cotest/trunk wc1
A wc1\src
A wc1\src\hash.java
A wc1\src\theplan.c
A wc1\readme.txt
Checked out revision 118.

# check out working copy 2
svn co svn://server/testrepo/cotest/trunk wc2
A wc2\src
A wc2\src\hash.java
A wc2\src\theplan.c
A wc2\readme.txt
Checked out revision 118.

# edit and commit a file in working copy 2
vi wc2\readme.txt
svn ci wc2 -m"checkout-as-update test"
Sending wc2\readme.txt
Transmitting file data .
Committed revision 119.

# checkout on working copy 1 now acts like update
svn co svn://server/testrepo/cotest/trunk wc1
U wc1\readme.txt
Checked out revision 119.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 29 22:12:30 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.