From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: [Fwd: Re: HEAD update blocked]
Date: Thu, 08 Apr 2004 07:39:00 -0000 [thread overview]
Message-ID: <407501C4.5080500@eCosCentric.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
I recommend not committing any new patches for the moment. Even without
potential corruption of the particular commit, it may be reverted if
there's a restore from backup. I'll try to remember to notify folks once
things are back to normal.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
[-- Attachment #2: Re: HEAD update blocked --]
[-- Type: message/rfc822, Size: 3252 bytes --]
From: Jason Molenda <jason-gcclist@molenda.com>
To: law@redhat.com
Cc: David Edelsohn <dje@watson.ibm.com>, Gabriel Dos Reis <gdr@integrable-solutions.net>, overseers@gcc.gnu.org
Subject: Re: HEAD update blocked
Date: Wed, 7 Apr 2004 22:36:48 -0700
Message-ID: <20040407223648.A64292@molenda.com>
On Wed, Apr 07, 2004 at 11:20:19PM -0600, law@redhat.com wrote:
> I'd recommend bringing the machine down and forcing an fsck of all the
> relevant filesystems. Unfortunately, I'm 1500 miles away and don't
> trust myself to set that up and deal with any potential consequences
> remotely.
A failing disk is a big risk particularly the CVS repository disk.
I would not be opposed to turning off all CVS access until some
capable RH person can look at it personally tomorrow morning.
Opinions?
Does anyone know for certain that such a knowledgable person
can be found?
Jason
next reply other threads:[~2004-04-08 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 7:39 Jonathan Larmour [this message]
2004-04-08 7:49 ` Gary Thomas
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=407501C4.5080500@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.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).