"Eric S. Raymond" <esr@thyrsus.com> writes:
> > 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.
Why, thank you.
> 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."
Actually, it should be genericized a bit by striking the " and
database recovery". This can happen for various reasons that don't
require recovery (network outage, etc.).
> And the answer should end by noting that only svn update refreshes the
> text-base.
Would be so kind as to work up a patch against www/project_faq.html?
I'd be happy to review/apply it after you've done so. If you feel
like taking the very text of the description I mailed, go for it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 10 08:15:48 2004