From: "Eric S. Raymond" <esr@thyrsus.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Alexandre Oliva <oliva@gnu.org>,
Bernd Schmidt <bernds_cb1@t-online.de>,
GCC Development <gcc@gcc.gnu.org>,
fallenpegasus@gmail.com
Subject: Re: Repo conversion troubles.
Date: Sat, 21 Jul 2018 02:04:00 -0000 [thread overview]
Message-ID: <20180720234849.GC3840@thyrsus.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1807202136100.27257@digraph.polyomino.org.uk>
Joseph Myers <joseph@codesourcery.com>:
> On Mon, 9 Jul 2018, Alexandre Oliva wrote:
>
> > On Jul 9, 2018, Jeff Law <law@redhat.com> wrote:
> >
> > > On 07/09/2018 01:57 PM, Eric S. Raymond wrote:
> > >> Jeff Law <law@redhat.com>:
> > >>> I'm not aware of any such merges, but any that occurred most likely
> > >>> happened after mid-April when the trunk was re-opened for development.
> >
> > >> I'm pretty certain things were still good at r256000. I've started that
> > >> check running. Not expecting results in less than twelve hours.
> >
> > > r256000 would be roughly Christmas 2017.
> >
> > When was the RAID/LVM disk corruption incident? Could it possibly have
> > left any of our svn repo metadata in a corrupted way that confuses
> > reposurgeon, and that leads to such huge differences?
>
> That was 14/15 Aug 2017, and all the SVN revision data up to r251080 were
> restored from backup within 24 hours or so. I found no signs of damage to
> revisions from the 24 hours or so between r251080 and the time of the
> corruption when I examined diffs for all those revisions by hand at that
> time.
Agreed. I don't think that incident is at the root of the problems.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
next prev parent reply other threads:[~2018-07-20 23:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 19:19 Eric S. Raymond
2018-07-09 19:40 ` Jeff Law
2018-07-09 19:57 ` Eric S. Raymond
2018-07-09 20:01 ` Jeff Law
2018-07-09 20:06 ` Eric S. Raymond
2018-07-09 19:46 ` Bernd Schmidt
2018-07-09 19:59 ` Eric S. Raymond
2018-07-10 1:13 ` Alexandre Oliva
2018-07-20 21:48 ` Joseph Myers
2018-07-21 2:04 ` Eric S. Raymond [this message]
2018-07-10 8:20 ` Jonathan Wakely
2018-07-10 8:34 ` Jonathan Wakely
2018-07-10 10:48 ` Eric S. Raymond
2018-07-20 22:06 ` Joseph Myers
2018-07-09 20:04 ` Richard Biener
2018-07-09 20:20 ` Eric S. Raymond
2018-07-10 4:57 ` Richard Biener
2018-07-10 11:22 ` Philip Martin
2018-07-20 21:43 ` Joseph Myers
2018-07-20 23:48 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180720234849.GC3840@thyrsus.com \
--to=esr@thyrsus.com \
--cc=bernds_cb1@t-online.de \
--cc=fallenpegasus@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=oliva@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).