This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: /cvs/gcc/gcc/gcc/ChangeLog,v restored
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: /cvs/gcc/gcc/gcc/ChangeLog,v restored
- From: law at redhat dot com
- Date: Mon, 16 Jul 2001 12:29:01 -0600
- cc: Tom Tromey <tromey at redhat dot com>, gcc at gcc dot gnu dot org, overseers at sources dot redhat dot com
- Reply-To: law at redhat dot com
In message <Pine.LNX.4.33.0107161858170.26033-100000@kern.srcf.societies.cam.
ac.uk>you write:
> On Mon, 16 Jul 2001 law@redhat.com wrote:
>
> > As I've said, multiple times, there is no way to physically mount the dri
> ve
> > in the cabinet. The drive is sitting here on my desk.
> >
> > Specifically what file(s) do you need to fix the PR.
>
> The whole of what was /sourceware/www/gcc/ml/ (i.e., about 2 Gbyte of
> data) - since I don't see any more reliable way of identifying individual
> message files that may be corrupt than comparing against the old ones, and
> replacing the contents of directories with no genuine changes
> (regeneration etc.) from the old disk (then applying less reliable
> heuristics to March/April archives).
Well, there's no chance I'll be able to upload that much data across
my puny link.
So what would you like to see us do?
> > Things are better in some ways now, but worse in others.
>
> Who *is* supposed to be responsible for boring but essential tasks such as
> backups and restoring from them?
That is supposed to be our sysadmin staff (it's the one thing they are
on the hook for).
jeff