Keith Johnson wrote on Wed, Feb 25, 2015 at 13:14:56 -0600:
> On Wed, Feb 25, 2015 at 12:33 PM, Andreas Stieger
> wrote:
>
> > Hi,
> >
> > Am 25. Februar 2015 18:48:37 MEZ, schrieb Keith Johnson > >:
> >
> > >When having a 4th person do a checkout recently, the process (via
> > >tortoisesvn) bom
[snip]
> First step is to *write lock* the old repository, to avoid
> accumulating history on broken history.
Absolutely - and make sure the lock stays locked forever more.
> You will be *breaking history* due to the corrupted repo. You
> should ideally create a new repo to do the repairs in,
On Wed, Feb 25, 2015 at 2:14 PM, Keith Johnson wrote:
> Hi Andreas, thanks for the response.
>
> The revision in question is over a year old, so I'm not sure I can put it
> back exactly as it was (guess all I can do is try my best). I assume
> there's no way to actually get historical data from
On Wed, Feb 25, 2015 at 12:33 PM, Andreas Stieger
wrote:
> Hi,
>
> Am 25. Februar 2015 18:48:37 MEZ, schrieb Keith Johnson >:
>
> >When having a 4th person do a checkout recently, the process (via
> >tortoisesvn) bombed out with a path to a revs file (db/revs/0/586 or
> >something) and input/out
Hi,
Am 25. Februar 2015 18:48:37 MEZ, schrieb Keith Johnson :
>When having a 4th person do a checkout recently, the process (via
>tortoisesvn) bombed out with a path to a revs file (db/revs/0/586 or
>something) and input/output error.
>
>It became evident very quickly that this was a result of ba
Hello folks. I'm not currently a subscriber, and therefore would
appreciate cc's. I will of course respond back to the list.
Here is the gist of my situation. I have a relatively small repo, a little
over 1000 commits, 6G total or so (fair amount of binary data), very few
users (3).
When havin
