From owner-cvs-all Tue Feb 26 13: 9:41 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 A727037B417; Tue, 26 Feb 2002 13:09:26 -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 g1QL8oD35374; Tue, 26 Feb 2002 16:08:51 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 26 Feb 2002 16:08:50 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Matthew Dillon Cc: Garance A Drosihn , Alfred Perlstein , Julian Elischer , Jake Burkholder , 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: <200202262103.g1QL3SN97161@apollo.backplane.com> 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 Dillon wrote: > > :The important observation here is that when a change is contentious, it > :doesn't hurt to not commit it immediately, but to wait. In fact, that's a > > That's a wonderful comment, but it is not what John has caused to > happen the last N times. I am not joking about the whole 'crying wolf' > problem. I do not believe John any longer has the right to force an > indefinite delay and that is essentially what has happened to just > everything I've ever tried to do in SMP land. Perhaps I'm not recalling an earlier incident. The number of times where I've asked you not to commit something because something identical exists in a jhb tree is precisely 1. That's not a very big N. One hates to dig up long dead issues, but could you expound on what you are referring to? > I don't expect things to mesh perfectly but I have said on more then > one occassion that I do not have a problem working with people to > fix compatibility issues. I do not believe that such issues should > prevent a commit from occuring, especially not if the code in question > is sitting stale in somebody's tree for months. It is an inappropriate > burden on the person who IS actively working on the code in question > to force him to wait a week for every single commit, every time. Every single commit, every time? For N of 1? > That is why I made the commit, and why I feel I have a right to make > the commit. 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