-----Original Message-----
From: news [mailto:news@sea.gmane.org]On Behalf Of Nick Patavalis
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.
---------------------------------------------------------------------
The problem is probably more subtle than it appears. As you noted, you are
not getting your "svn cp" to be rejected all the time that the WC is not up
to date. And when I tested "svn cp" from a mixed-revision WC with
modifications to a URL, it worked for me. So you probably need to do more
investigation to find out what the problem really is. (And log it as a bug
report, as the message you are getting is not describing what the real
problem is.)
As for WCs, you can tell whether they have mixed revisions by running
"svnversion /...". If all elements are at one revision, it prints that
number, but if there are more than one revisions, it prints the minimum and
maximum. E.g., "155:157". If any of the elements have been modified
relative to BASE, an "M" is appended.
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 5 17:45:30 2005