Re: Possible bug: "svn status" returns no changes when there are

On Wed, 2008-02-27 at 07:50 +0100, Jorge J. Gomez Sanz wrote:
> In any case, I am surprise that "svn commit" on the rev 39 file did not
> trigger any error. If two different versions were being handled, it should
> have had protested.

The key here is there were no changes in the r39 (sampleB) working copy,
so on "svn ci" the client says "OK, nothing to do" and quits without
ever contacting the server. If, however, ConversationManagement.java was
modified in sampleB, "svn ci" would fail the commit with a message
something like:

svn: Out of date: 'ConversationManagement.java' in transaction <id>

Mark

-- 
----------------------
Mark S. Reibert, Ph.D.
svn_at_reibert.com
----------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org