From owner-cvs-all Tue Feb 26 14: 6:37 2002 Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6999E37B405; Tue, 26 Feb 2002 14:06:30 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g1QM5xD36433; Tue, 26 Feb 2002 17:05:59 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 26 Feb 2002 17:05:58 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Matthew Jacob Cc: Julian Elischer , Garance A Drosihn , Alfred Perlstein , Jake Burkholder , Matt Dillon , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.c mp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.h pcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.c intr_machdep.h npx.c src/sys/kern ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 26 Feb 2002, Matthew Jacob wrote: > > I would also like to have core take a stand that having code in P4 isn NOT > > the same as publishing it. P4 is an aid to the developer to do PRIVATE > > work. As long as the work is in P4 it is up to the developer to > > keep it in sync with -current. From the project's perspective > > work in P4 doesn't exist. > > FWIW, concur. Per Julian's request, I've reposted my solicitation for comments on the version control system issue on -current. I would appreciate it if you'd send responses to that. The goal is to end up with a set of guidelines for people who choose to use an external version control system so that they can know they're taking reasonable steps to publicize and expose their work in an appropriate and project-centric way. I think one can't completely rule out collaboration in P4 -- for example, the TrustedBSD component of the Perforce repository really does represent the best way to get the work done. On the other hand, that's not necessarily any different from a few people working on a project who use an external CVS repository. Please give a few minutes thought, take a look at the suggestions in my e-mail, and respond there. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message