Date: Thu, 17 Oct 2002 10:28:03 -0400
Message-Id: <200210171428.g9HES3525038@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <200210171423.QAA21208@lws256.lu.erisoft.se> (message from Martin
	Stromberg on Thu, 17 Oct 2002 16:23:57 +0200 (MET DST))
Subject: Re: stub.asm patch for 2.02 => 2.04
References:  <200210171423 DOT QAA21208 AT lws256 DOT lu DOT erisoft DOT se>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


Gee, now I have to think about it ;-)

Ok, I have no problem with bumping it to 2.04.  I think the original
reason was to provide something for tools to read to see if there was
an API change (new stubbable variables in the header, mostly).  I
doubt there will be any for 2.04, so simply changing it to 2.04 and
leaving it there through the release should be fine.

I don't think we need to try to be clever about bumping it for alphas
or internal changes.

I don't see much need for shrinking the stub any further, unless we
need to add something else into the new space.  But feel free to post
the patches anyway ;-)