Well, naturally, our first incident of client-side corruption in a
long time happens two days before Alpha :-).
If we can track down and fix the source of Kevin's problem before
Monday, then great. If not, though, we can't release Alpha with a
known bug like this, so we should devote all resources to tracking it
down.
We might establish that the problem is due to a particular
revision(s), which could be reverted for release, and then worked on
at our leisure. But I tend to think that if we pinpoint the
revisions, we have pinpointed the cause, and should just work on the
fix from there -- I mean, how long can it take?
So. I have a few outstanding changes related to issue #494, which I
will commit up (will watch carefully for corruption) when ready, and
then I will start looking at recent commits to see what might be
causing this corruption bug. Kevin in particular, I hope you will be
able to join the search -- because you have the working copy where it
happened once. And everyone else, in particular :-), I hope you can
help too. See my earlier posts for a recipe for discovering corrupt
text-bases in your working copy (and feel free to test that recipe by
deliberately mucking up some text bases temporarily -- I haven't
tested it like that, but will).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 12 22:20:26 2002