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

Commits that aren't?

From: Tom Brunet <tomab_at_cs.wisc.edu>
Date: 2004-04-15 20:13:25 CEST

I'm running WinXP and connecting through SSH to a repository on a Redhat
Linux box. I can check out files from the repository just fine. I
commit and it goes through the messages saying I added files, transmits
file data, and I get the message "Committed revision 3.".

The problem is that after this, the actual repository is only at
revision 2, and that commit never occurred at the server, even though my
client told me that it did. Now, my working copy thinks it's at
revision 3, so I can't perform any more commands since the server
apparently doesn't know about revision 3. The only way to recover my
local copy is to checkout a fresh copy (which is at revision 2 without
my changes). Commits done by manually uploading the files to the Linux
box and doing commits on the server work fine.

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?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 15 20:17:42 2004

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.