On 3/15/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:
It does tell me what the last revision number was that it dumped
but, there is lots of stuff in the repository after that revision that I
don't want to lose.
I have never had to recover a problem like this. If you can dump up to
the problem, then skip that revision and dump what comes after, you
might be able to fix the problem. Just load the first dump file. Do
some random commit to use up the next revision number, and then load the
second dump file. The random commit is not strictly necessary if you do
not care about the revision numbers changing.
It appears that there are other revisions after my corrupt revision that
also have that same issue. It would be nice if there was a repair
option that could just fix it for me :) ... but that would be too
easy. I can dump pieces of the repo so I will work on piecing it back
together from that unless someone else has any better suggestions.
Thanks for your help.
This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer. Messages sent to and from Stoneware, Inc.
may be monitored.
Received on Thu Mar 15 20:09:38 2007