From owner-freebsd-current Fri Feb 9 2:13:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 6678F37B503 for ; Fri, 9 Feb 2001 02:13:29 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA21270; Fri, 9 Feb 2001 11:13:26 +0100 (MET) Date: Fri, 9 Feb 2001 11:13:26 +0100 (CET) From: Harti Brandt To: Jeroen Ruigrok van der Werven Cc: Harti Brandt , Subject: Re: Current buildworld broken In-Reply-To: <20010209104221.B30191@lucifer.bart.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Feb 2001, Jeroen Ruigrok van der Werven wrote: JRvdW>-On [20010207 11:00], Harti Brandt (brandt@fokus.gmd.de) wrote: JRvdW>> JRvdW>>With a freshly CVSuped current I get: JRvdW>> ... JRvdW> JRvdW>You are probably caught in between commits. JRvdW> JRvdW>Always cvsup after such problems, after you waited an hour or so for JRvdW>your favourite cvsup mirror up pick up any further commits, and then try JRvdW>again, and THEN report things like this. Saves traffic. :) I did report after cvsupping twice, but I had a cvs that dumped core in deep subdirectories and did not tell me about that. In my feeling cvs has become quit unstable for a couple of months now... harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message