Re: Commits that aren't?

* Tom Brunet <tomab@cs.wisc.edu> [2004-04-15 12:14]:
> Is there any reason why my client would tell me that it committed a
> revision when in fact it didn't? Why does the client update its state
> to a revision that is non-existent? Any suggestions for how to get
> these commits to actually happen?

Are you sure the client is committing to the repository you think it is? What
is the output of 'svn info' when you run it on your working copy? Can you get
information about revision 3 via the client after you commit it, i.e. do 'svn
log' and 'svn diff' show what you would expect?

-- Mike

-- 
Michael W. Thelen
It is a mistake to think you can solve any major problems just with potatoes.
                -- Douglas Adams