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

Copying commited WC

From: Nick Patavalis <npat_at_inaccessnetworks.com>
Date: 2005-01-04 16:39:46 CET

Trying to copy a WC that was just commited fails, complaining that the
checked-in files are not up to date.

Furthermore there seems to be no way, given a WC, to know if a
subsequent "cp" command will succeed or fail, without knowing if
commits were previously performed from the WC. As a result there seems
to be no easy way to write a script that copies a WC to a repo-path.

Example:

 1. svn co svn://server/repo/proj/trunk ./proj
 2. svn co svn://server/repo/proj/trunk ./proj1
 3. cd ./proj1
 4. vi foo.c
 5. svn -m "Modified foo.c" ci
 6. cd ../proj
 7. vi bar.c
 8. svn cp . svn://server/repo/proj/tags/tag1
 9. svn -m "Modified bar.c" ci
10. svn cp . svn://server/repo/proj/tags/tag2

Step (8) fails, complaining that the file "bar.c" is not up to date.
On the other hand (6) succeeds, regardless of the fact that "foo.c" is
obviously not up to date.

Can somebody suggest a formal way (e.g. script) that, given a working
copy, tests if a subsequent "cp" command will fail for the reason
shown above?

Thnaks in advance
/npat

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 4 16:48:38 2005

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