Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Tue, 3 Feb 2004 23:11:34 +0100
From: =?ISO-8859-15?Q?Andr=E9?= Malo <nd@perlig.de>
To: dev@httpd.apache.org
Subject: Re: cvs commit: httpd-2.0/server core.c
Message-Id: <20040203231134.4bde6bcf.nd@perlig.de>
In-Reply-To: <Pine.GSO.4.58.0402031643100.4387@cobra.cs.Virginia.EDU>
References: <20040125220339.91019.qmail@minotaur.apache.org>
	<6.0.2.0.2.20040203133039.049a8ec0@pop3.rowe-clan.net>
	<Pine.GSO.4.58.0402031643100.4387@cobra.cs.Virginia.EDU>
Organization: TIMTOWTDI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

* Cliff Woolley <jwoolley@virginia.edu> wrote:

> On Tue, 3 Feb 2004, William A. Rowe, Jr. wrote:
> 
> > Uhmmm, this isn't an MMN bump :)  If you were adding this new
> > structure *type* as a member of another structure (say as the last
> > member of the conn_rec) and the structure grew (in such a way that
> > folks could be blindly oblivious to the fact that conn_rec just got a
> > bit bigger), that's an MMN bump.  It's not the case here.
> 
> I disagree.  If you add a function to the API without bumping the MMN,
> then how is a module that wants to use the new function if it exists and
> yet still compile if it doesn't supposed to work?  It can't.

Yes, that's my understanding as well: major bumps break backwards compat and
minor bumps keep forward compat.

nd