Date: Thu, 07 Jun 2001 08:04:16 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Dima Dorfman <dima@unixfreak.org> Cc: hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? Message-ID: <90455.991893856@critter> In-Reply-To: Your message of "Wed, 06 Jun 2001 19:41:10 PDT." <20010607024110.5403A3E0B@bazooka.unixfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010607024110.5403A3E0B@bazooka.unixfreak.org>, Dima Dorfman write s: >Poul-Henning Kamp <phk@critter.freebsd.dk> writes: >> In message <20010605013148.A49246@dragon.nuxi.com>, "David O'Brien" writes: >> >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: >> >> Is there any reason not to MFC the new md(4) functionality >> > >> >Zero reason not to. >> >> Others see it differently, it would seriously break a lot of >> people who are using -stable in embedded applications. >> >> If we have abandoned the "no changes to API or ABI in -stable" >> paradigm, it would be a good idea, but it serious rains on that >> rule... > >I don't think it would be much of a practical problem for anyone since >the old behvior can be emulated with the new md pretty easily, but >you're right that it isn't appropriate to break compatibility in >-stable. It's probably possible to retrofit the old behavior into the >new code, but I think that's too much evil for too little gain. Well, I see that we just ripped out the "wd" compat bits, so I guess we don't care about ABI/API stability that much in -stable any more... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90455.991893856>