From owner-freebsd-current  Tue Jul 15 09:51:02 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA09846
          for current-outgoing; Tue, 15 Jul 1997 09:51:02 -0700 (PDT)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09816;
          Tue, 15 Jul 1997 09:50:45 -0700 (PDT)
Received: from austin.polstra.com (jdp@localhost)
	by austin.polstra.com (8.8.6/8.8.5) with ESMTP id JAA22020;
	Tue, 15 Jul 1997 09:50:00 -0700 (PDT)
Message-Id: <199707151650.JAA22020@austin.polstra.com>
To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>
cc: FreeBSD-current <current@freebsd.org>, peter@freebsd.org
Subject: Re: Yet one CVSup false fetch 
In-reply-to: Your message of "Tue, 15 Jul 1997 20:35:47 +0400."
             <Pine.BSF.3.96.970715203043.842A-100000@nagual.pp.ru> 
References: <Pine.BSF.3.96.970715203043.842A-100000@nagual.pp.ru> 
Date: Tue, 15 Jul 1997 09:50:00 -0700
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Checkout src/lib/libedit/termcap.h
> 
> This file not belongs to -current according "cvs co", but fetches
> from freefall again even when removed.
> 
> Repository or CVSup must be fixed, please...

OK, I fixed it in the repository with a "cvs update; cvs rm"
combination.  The default branch had been cleared in the RCS file,
even though the file was still on the vendor branch.  I don't know
why.  We know of CVS bugs that can cause this, but I don't think
they applied to this case.  Sigh.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth