From: Jeff Mitchell <jeffrey.mitchell@gmail.com>
Date: Thu, 28 Mar 2013 13:52:47 GMT
Subject: Re: propagating repo corruption across clone
Message-ID: <CAOx6V3Yx5CYGQXMY_LUy0mxpROZveYjitdAqY_hC4dRcMU9sXw@mail.gmail.com>
In-Reply-To: <1364410309241-7580845.post@n2.nabble.com>

On Wed, Mar 27, 2013 at 2:51 PM, Rich Fromm <richard_fromm@yahoo.com> wrote:
> Nevertheless, I will try to contact Jeff and point him at this.  My initial
> reading of his blog posts definitely gave me the impression that this was a
> --mirror vs. not issue, but it really sounds like his main problem was using
> --local.

Actually, I wasn't using --local, I just wasn't using --no-local, as I
mixed up that and --no-hardlinks (which lies somewhere between, but is
still not the same as using file://).

It's entirely possible that you read the posts before I updated them.

Also, keep in mind, if you're evaluating what you're doing, that the
system we have was not set up to be a backup system. It was set up to
be a mirror system. With proper sanity checking, it would have acted
in a decent capacity as a backup system, but that wasn't why it was
set up, nor how it was set up.