Re: Out of date errors just after a revert

C. Michael Pilato <cmpilato@collab.net>:
> "Eric S. Raymond" <esr@snark.thyrsus.com> writes:
>
> > Isn't revert supposed to refresh the baseline copy? How can it be
> > out of date at that point?
>
> Revert simply rebuilds the working from from the pristine text-base in
> the .svn directory. If you had a commit that went sour between the
> time the new revision was added in the server, and the time your
> client performed its post-commit admin tasks, then it's possible that
> you have already committed the very changes you are trying now to
> commit.
>
> Try reverting again, and then running 'svn update'. Chances are good
> that the server will send you the very changes you're trying to send
> *it*. :-)

Ahhhh. So only "svn update" refreshes the baseline. I grok.

That procedure worked, and you've given a good explanation. Would you please
add it to the FAQ? I am unlikely to be the last person to trip over this.
The question should probably be something like,

"After a failed commit and database recovery, I get "out-of-date" errors
when trying to finish the commit."

And the answer should end by noting that only svn update refreshes the
text-base.

-- 
		Eric S. Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org