From owner-cvs-all Tue Jan 27 08:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17178 for cvs-all-outgoing; Tue, 27 Jan 1998 08:39:45 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17136 for ; Tue, 27 Jan 1998 08:39:30 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id AAA15237; Wed, 28 Jan 1998 00:36:50 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199801271636.AAA15237@spinner.netplex.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Polstra cc: committers@FreeBSD.ORG Subject: Re: Is this a new CVS bug? In-reply-to: Your message of "Tue, 27 Jan 1998 08:11:22 PST." <199801271611.IAA17726@austin.polstra.com> Date: Wed, 28 Jan 1998 00:36:50 +0800 From: Peter Wemm Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk John Polstra wrote: > I ran into this CVS bug on freefall this morning. > > Last night I checked out a few things from the RELENG_2_2 branch: > > freefall$ ls -F > CVS/ brandelf/ include/ sys_i386/ sys_sys/ > > I merged in some changes from -current, but didn't commit them. This > morning I did a cvs update to make sure there hadn't been other > commits to any of the files during the night: > > freefall$ cvs -q upd -Pd -r RELENG_2_2 > U Makefile > U brandelf.1 > U brandelf.c > M brandelf/brandelf.c > M include/Makefile > A include/elf.h > A sys_i386/include/elf.h > A sys_sys/elf32.h > M sys_sys/imgact_elf.h > > freefall$ ls -F > CVS/ brandelf/ brandelf.c sys_i386/ > Makefile brandelf.1 include/ sys_sys/ > > As you can see, it bogusly checked out the brandelf files into my > top-level directory. > > Is this a new bug, or was it already known? You ran this on freefall, yes? If so, then that's still the old cvs on there, so it's not a new bug. :-) Whether or not this is a bug or feature depends on how you look at it. cvs has (for a while) created a CVS/ directory in the top level directory with a path to the module in question. Doing a 'cvs update -d -P' in the top directory causes the exact effects that you describe. IMHO, it's a bloody pest and in my book it's a bug. Creating CVS/Root is fine for the top directory, but causes more trouble than it's worth. > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > Cheers, -Peter -- Peter Wemm Netplex Consulting