From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29446 invoked by alias); 20 Jul 2004 19:45:43 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 29436 invoked from network); 20 Jul 2004 19:45:43 -0000 Received: from unknown (HELO cgf.cx) (66.30.22.40) by sourceware.org with SMTP; 20 Jul 2004 19:45:43 -0000 Received: by cgf.cx (Postfix, from userid 201) id 930451BA7F; Tue, 20 Jul 2004 15:44:55 -0400 (EDT) Date: Tue, 20 Jul 2004 19:45:00 -0000 From: Christopher Faylor To: Jim Blandy Cc: overseers@sources.redhat.com Subject: Re: GDB CVS needs a kick Message-ID: <20040720194455.GA11921@trixie.casa.cgf.cx> Mail-Followup-To: Jim Blandy , overseers@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2004-q3/txt/msg00048.txt.bz2 On Tue, Jul 20, 2004 at 12:35:26PM -0500, Jim Blandy wrote: >Is there a stale lock file lying around? There were two of them, actually. Two cvs processes were going crazy. They are nuked now. cgf >zenia:gdb$ cvs commit ChangeLog rs6000-tdep.c >Waiting for Emacs...Done >cvs commit: [17:18:59] waiting for anoncvs's lock in /cvs/src/src/gdb