Tom,
This often happens because someone does
$ svn commit -m "log message"
...
Committed revision 3.
$ svn log
------------------------------------------------------------------------
r2 | jrandom | 2004-04-12 15:31:15 -0500 (Mon, 12 Apr 2004) | 1 line
Reimplement backhoe in ADA.
------------------------------------------------------------------------
r1 | jrandom | 2004-04-12 13:00:00 -0500 (Mon, 12 Apr 2004) | 1 line
Import backhoe.
------------------------------------------------------------------------
$
They see that the logs only go up to r2, and they wonder what happened
to r3. The answer is that their working copy directory "." is still
at r2 (even though some files under it may be at r3), and by default
'svn log' takes its upper revision from ".".
If you run 'svn update' and then rerun 'svn log', you should be fine.
This burns people over and over. I sometimes wish we'd just defaulted
to HEAD instead of the base revision of ".", but it's a bit late now.
-Karl
Tom Brunet <tomab@cs.wisc.edu> writes:
> 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?
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 15 23:04:16 2004