Lukas Ruf <ruf@rawip.org> writes:
> Crawling the documentation led me to to 'svn update'.
>
> This however, resulted in 'reverts'. So, I interrupt this process by
How did running 'svn update' result in reverts? That should never
happen; at the worst, you should get conflicts, but not reverts.
> The problem now is: I cannot commit the local modifications.
>
> komsys-pc-ruf:2.6.6!62> svn status -v -u CREDITS
> M * 165 165 ruf CREDITS
> Status against revision: 166
> komsys-pc-ruf:2.6.6!63> svn commit -m "saving CREDITS" CREDITS
> Sending CREDITS
> svn: Commit failed (details follow):
> svn: Your file or directory 'CREDITS' is probably out-of-date
> svn:
> The version resource does not correspond to the resource within the
> transaction. Either the requested version resource is out of date
> (needs to be updated), or the requested version resource is newer
> than the transaction root (restart the commit).
>
> My question: how can I solve this problem without losing my changes?
Running 'svn update' shouldn't lose your changes. We'd need more
details to figure out why you felt it would, though...
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 18 18:06:03 2004