From owner-freebsd-ports Sun Sep 29 17:43:55 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02390 for ports-outgoing; Sun, 29 Sep 1996 17:43:55 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA02352 for ; Sun, 29 Sep 1996 17:43:52 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id RAA01359; Sun, 29 Sep 1996 17:43:41 -0700 (PDT) Message-Id: <199609300043.RAA01359@austin.polstra.com> To: Andreas Klemm cc: ports@freebsd.org Subject: Re: cvsup doesn't remove old patches, doesn't put things in the Attic In-reply-to: Your message of "Sun, 29 Sep 1996 22:20:01 +0200." Date: Sun, 29 Sep 1996 17:43:41 -0700 From: John Polstra Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Sorry, got the wrong subject .... > > Here again with correct subject, to address the right people... OK, I suppose I'd better repeat my reply with the new subject ... I think I know what's going on. It's not really a bug. First of all, what _are_ those files "patch-a[b-d],v" on your system? Are they really patches for xpaint? Why don't they exist in the CVS repository? Even if they had been removed with "cvs rm", they should still exist in the Attic. I will assume that they really are old patches, and that somebody erroneously deleted them from the CVS repository, instead of using "cvs rm" as they should have done. Still, I think CVSup did the right thing. Here is what I think was the sequence of events: 1. The patches existed both in the main repository, and in your local copy. 2. Somebody deleted the patches from the main repository, but they remained in your local repository. 3. You started using CVSup for the first time. In that case, CVSup would consider "patch-a[b-e],v" to be extra, unknown files in your local repository. It didn't create them, and there's no trace of them in the master repository. It doesn't know anything about them -- and so it won't delete them. It will never delete anything that it doesn't know about. That's what I think happened. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth