Date: Tue, 26 Feb 2002 16:53:01 -0500 From: Bosko Milekic <bmilekic@unixdaemons.com> To: Julian Elischer <julian@elischer.org> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Warner Losh <imp@harmony.village.org>, Jake Burkholder <jake@locore.ca>, 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 ... Message-ID: <20020226165301.A29286@unixdaemons.com> In-Reply-To: <Pine.BSF.4.21.0202261117520.94891-100000@InterJet.elischer.org>; from julian@elischer.org on Tue, Feb 26, 2002 at 11:22:30AM -0800 References: <200202261822.g1QIMcK95505@apollo.backplane.com> <Pine.BSF.4.21.0202261117520.94891-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 26, 2002 at 11:22:30AM -0800, Julian Elischer wrote: > JHB has had a 8 months to check in his stuff (hey the preemtion stuff was > done in June) and since then it's only effect on the project has been to > stiffle and stop all other development in the area. > > I blame P4 for this in part. > HE thinks he is being transparent to the rest of the community whereas he > has a total viewing public of about 4. OK guys, now just a second. JHB clearly posted that _the preemption code is not ready yet_. What the heck are you trying to do? Make him commit broken code? Of all the people on this list, I would have thought you (Julian) to be the one that would most understand that sometimes, you just have to do it the `big changes all at once' way, as you have been doing, clearly, with KSE. It's understandable for pre-emption as well and the fact that JHB is taking his time to make sure that it's not broken on every architecture shouldn't be something that he should get sh*tted on for. Whether there are other (not-so-related) changes in the p4 repo that need to be weeded out and committed is another story. But don't blow this out of proportion, please. > Consider this a test case. > Core is appealled to. The blocking action of JHB's (good) work is doing > more damage to the project than good. We need to be able to proceed > without waiting for him... > > > > On Tue, 26 Feb 2002, Matthew Dillon wrote: > > > > > : > > :In message <200202261806.g1QI6GL94130@apollo.backplane.com> Matthew Dillon writes: > > :: I will not back it out. JHB has had issues with every single goddamn > > :: thing I've tried to do that has been SMP related. JHB has had > > :: patches going stale in P4 related to just about every file I've ever > > :: had to touch. > > :: > > :: He has cried wolf one too many times. It is totally inappropriate for > > :: JHB to put a lock on the entire SMP subsystem. > > :: > > :: JHB needs to get his act together. > > : > > :Matt, > > : These patches are in dispute and should not have been > > :committed. Please respect the FreeBSD process and back them out. > > :This is totally unacceptible in the prioject. While you may have some > > :points about how smpng has been run, they do not justify this flagrant > > :violation of long standing project proceedures. Please back them out > > :now. > > : > > :Warner > > > > I can only repeat what I've now said about a billion times. JHB has > > no right to arbitrarily hold up my SMP contributions. If he had done > > it just once it would not have been a problem. I have no problem working > > with developers who are truely interested in working together. > > > > But he has done it four times now and that is one time too many. I > > do not believe that he has the right. > > > > Core will have to back this out. And if core does back this out I > > promise you that I will not rest until it goes back in. > > > > -Matt > > Matthew Dillon > > <dillon@backplane.com> > > > -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020226165301.A29286>