Date: Wed, 5 Dec 2001 12:23:39 -0500 From: Mike Barcroft <mike@FreeBSD.ORG> To: Luigi Rizzo <luigi@FreeBSD.ORG> Cc: Warner Losh <imp@harmony.village.org>, Robert Watson <rwatson@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/conf options.i386 src/sys/i386/i386 swtch.s trap.c src/sys/net if.h netisr.h src/sys/sys systm.h src/sys/i386/include asnames.h src/sys/kern kern_clock.c src/sys/dev/fxp if_fxp.c src/sys/pci if_dc.c if_dcreg.h if_sis.c ... Message-ID: <20011205122339.G63148@espresso.q9media.com> In-Reply-To: <20011205085557.B63639@iguana.aciri.org>; from luigi@FreeBSD.ORG on Wed, Dec 05, 2001 at 08:55:57AM -0800 References: <Pine.NEB.3.96L.1011204102208.62227B-100000@fledge.watson.org> <200112050852.fB58qrM79607@harmony.village.org> <20011205085557.B63639@iguana.aciri.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Luigi Rizzo <luigi@FreeBSD.ORG> writes: > I have posted to -core a version of this code which is targeted to > -current, and I do plan to add it there as well. > > I have not done the commit yet first because i got no reply from > core on the topic, secondly (and more importantly) because the > -current version does not perform as well as the one for -stable, > and might require some redesign. It's not surprising you've receive no reply from -core, as it's not a body intended to review code. Please post your patches to -arch. > Let me also say that I have a hard time following the logic below: > > > : Needless to say, I have some objection to this work going into -STABLE > > : before -CURRENT; do you have a schedule for completing the merge into > > : -CURRENT so this work isn't lost when we get to 5.0-RELEASE? > > > I too have grave concerns about this. Can you please enlighten us as > > to your schedule? I'd hate to loose such a feature when we release > > 5.0-RELEASE. > > so would you rather not have this feature at all than risk of losing > it in one year's time on 5.0-R ? If I had not committed this code > now (or soon) it would have been lost for STABLE as well, because > the time (and testing resources) I have to work on this project will > be largely reduced in a week's time. The Committers Guide clearly states "All commits should go to FreeBSD-CURRENT before being merged to FreeBSD-STABLE. No major new features or high-risk modifications should be made to the FreeBSD-STABLE branch." Best regards, Mike Barcroft 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?20011205122339.G63148>