Date: Tue, 28 Oct 1997 09:03:35 -0800 From: John Polstra <jdp@polstra.com> To: asami@cs.berkeley.edu Cc: jkh@time.cdrom.com, jfieber@indiana.edu, jkh@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: cvs commit: ports INDEX Message-ID: <199710281703.JAA21856@austin.polstra.com> In-Reply-To: <199710271104.DAA01994@bubble.didi.com> References: <199710271104.DAA01994@bubble.didi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199710271104.DAA01994@bubble.didi.com>, Satoshi Asami <asami@cs.berkeley.edu> wrote: > * Not so. Some rcs surgery by a suitably qualified (and scared) operator > * can fix this. (And IMVHO should, every now-and-then). > > I certainly would love to see that. Peter and John, do you think you > can clean up the recently added junk to ports/INDEX and > ports/www/apache-current/patches/patch-aa? NO! Whoever wants to do that is welcome to also reply to all the questions about mysterious complaints from CVSup and cvs concerning missing revisions. It is one thing to remove entire RCS files, but it's another thing entirely to muck around with undamaged RCS files which are merely inconvenient. If there existed at any time a revision 1.148, then somebody in the world has it checked out. And if that revision disappears from the repository, it causes mysterious problems for that person. The repository records the history of the project. Some of that history is sordid and wasteful, not to say idiotic. Too bad. We're not talking about enough disk space to justify surgery, in my opinion. Just leave it alone, and let it serve as a reminder to committers that they need to be careful. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710281703.JAA21856>