Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 09 Mar 2005 09:19:11 -0700
From:      Scott Long <scottl@samsco.org>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        des@des.no
Subject:   Re: cvs commit: src/sys/compat/linux linux_socket.c
Message-ID:  <422F21FF.6070908@samsco.org>
In-Reply-To: <20050309.085035.129356491.imp@bsdimp.com>
References:  <422E407B.4080507@portaone.com>	<86k6oht386.fsf@xps.des.no> <422F087F.9030906@portaone.com> <20050309.085035.129356491.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote:
> In message: <422F087F.9030906@portaone.com>
>             Maxim Sobolev <sobomax@portaone.com> writes:
> : and need this tool to upgrade otherwise perfectly working system(s).
> 
> As a veteran of ABI wars, I think that you have an unrealistic
> expectations about what can be done.  While an interesting goal, too
> many of the developers are hard wired to not even think about such
> considerations to make it successful.  We have a hard enough time
> making backward compatibility work, there's no hope for 'forward'
> compatability.
> 
> Warner

The goals I set forward for 5.x ABI stability are only meant for
backwards compatibility.  Trying to apply them to forwards compatibility
greatly restricts the amount of bugfixing and feature improvement that
can be done.  The only place where backwards and forwards compatiblity
are important are on the release/security braches.

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?422F21FF.6070908>