From owner-cvs-ports Sat Aug 19 05:03:03 1995 Return-Path: cvs-ports-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id FAA00765 for cvs-ports-outgoing; Sat, 19 Aug 1995 05:03:03 -0700 Received: from haywire.DIALix.COM (haywire.DIALix.COM [192.203.228.65]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id FAA00756 ; Sat, 19 Aug 1995 05:02:53 -0700 Received: (from peter@localhost) by haywire.DIALix.COM (8.7.Beta.11/8.7.Beta.11/DIALix) id UAA14379; Sat, 19 Aug 1995 20:02:33 +0800 (WST) Date: Sat, 19 Aug 1995 20:02:32 +0800 (WST) From: Peter Wemm To: Satoshi Asami cc: rgrimes@gndrsh.aac.dev.com, CVS-commiters@freefall.FreeBSD.org, cvs-ports@freefall.FreeBSD.org Subject: Re: cvs commit: ports/utils Makefile In-Reply-To: <199508191155.EAA27382@silvia.HIP.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: cvs-ports-owner@FreeBSD.org Precedence: bulk On Sat, 19 Aug 1995, Satoshi Asami wrote: > * BTW: suspending emacs and killing cvs is a 'bad thing', because it can > * leave a lock on the directory in ~ncvs.. (here, you can have this > * morning's conical hat back again.. :-). > > Uhh, is that so? I thought cvs will delete all the lock files if > "kill"ed cleanly (i.e., no "-9")...I have done this more than > once...(+_+;).... I dont know the exact circumstances, but I know it happens, right when it's least convenient.. Anyway, quitting emacs without saving would give you an opportunity to do a clean abort right then. I went to great pain in my cvsedit wrapper to get this right and maintain the behavior. I know there were two stray locks within the last day or two, but I can't remember where... Rod might... Cheers, -Peter > Satoshi (:>-* >