From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <200005182247.AAA09079@father.ludd.luth.se>
Subject: Re: Idea: Cutting edge DJGPP (alpha DJGPP?)
In-Reply-To: <200005111516.LAA23881@envy.delorie.com> from DJ Delorie at "May 11, 2000 11:16:04 am"
To: djgpp-workers AT delorie DOT com
Date: Fri, 19 May 2000 00:47:41 +0200 (MET DST)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

According to DJ Delorie:
> OK, then.  Note to all: if you are interested in working in djgpp's
> core, and can do remote CVS, and are willing and able to take
> responsibility for your patches, and think that the DJGPP community
> will trust you to Do The Right Thing, now's the time to speak up!

Ok, I'd like to be in that position.

Thanks for the cvs test directory!

How will we handle the scenario that a lot of alpha functionality has
been added to the cvs tree and then we need to fix a bug in v2.03?

Will weekly/monthly/"wheneversomthing has changed" builds of djdev be
produced?

Here's a list of what I remember is in the pipe to be added. Please
remind me of the other things I've forgotten.

1. FAT32 support (me)

2. Symlinks (Laurynas)

3. ???


Right,

							MartinS