X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Message-ID: <447dfb84$0$492$cc7c7865@news.luth.se>
From: Martin Str|mberg <ams AT speedy DOT ludd DOT ltu DOT se>
Subject: Re: DJGPP Modifications: second try
Newsgroups: comp.os.msdos.djgpp
References: <1148891367 DOT 146603 DOT 103410 AT j55g2000cwa DOT googlegroups DOT com>
User-Agent: tin/1.4.6-20020816 ("Aerials") (UNIX) (NetBSD/1.6Q (alpha))
Date: 31 May 2006 20:24:36 GMT
Lines: 35
NNTP-Posting-Host: speedy.ludd.ltu.se
X-Trace: 1149107076 news.luth.se 492 130.240.16.13
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

decker <bdeck AT lycos DOT co DOT uk> wrote:
> Here is the sad part:

>> Once Charles announced it will merge the ELF code into the CVS,
>> DJ Delorie recalled that they should release 2.04 before adding
>> new features.  I can agree with him, and let ELF code be released
>> with 2.05 soon after 2.04.
>>
>> The interesting part was, however, that until Charles spawned the
>> ELF discussion on the mailing list, nobody remembered that there is
>> a 2.04 pending for a few years now.

That's not true. At least not for me and probably not for anyone
else. We know very well that we have a new DJGPP release in the
works. However we don't have time, so time passes. And is likely to
continue to do so until somebody has time.

> Well, if that's the case, we _WILL_ fork. Otherwise, I'm afraid that my
> Social Security will mature faster than a *theoretical* 2.05 release
> ever would. Very sad. Very sad indeed.

There's no need to fork. Just make sure that the next version of DJGPP
is released. Then you can work on the next release of DJGPP.

The first thing to do is read the mail archives to figure out what
needs to be done. There are/were some web pages describing the status
as well, IIRC. Then subscribe to djgpp-workers and see if anyone have
time to answer questions.

Welcome and good luck!


Right,

						MartinS