Date: Mon, 16 Jun 1997 21:11:25 -0400 (EDT)
Message-Id: <199706170111.VAA27174@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: galbiati AT cse DOT ogi DOT edu
CC: eliz AT is DOT elta DOT co DOT il, djgpp AT delorie DOT com
In-reply-to: <Pine.SUN.3.95.970616013955.15752A-100000@blue.cse.ogi.edu>
	(message from Phil Galbiati on Mon, 16 Jun 1997 11:52:21 -0700 (PDT))
Subject: Re: Symify crashes in Windows Dos box
Precedence: bulk


> 1) I seem to recall reading that DJGPP uses its own implementation of
>    libc, of which you own the intellectual property rights.  Am I correct
>    in assuming that when fixing bugs in it, we must *NOT* under any
>    circumstances consult the source code for other implementations,
>    including Linux & BSD?

You can't copy code from other implementations.  The safest solution
is to have someone read and understand the other code, describe what
the other code does (without source) to the appropriate mailing list,
and let someone else figure out the sources.  That way, the people
that write the djgpp sources haven't seen the other sources.

However, lots of libc is based on the BSD sources, and is so stated in
the documentation, and the BSD copyright does not conflict with
DJGPP's copyright, so usually referencing the BSD implementation is
OK.

> 2) I also saw someplace that modifications to the DJGPP source must be
>    submitted as patches.  Is this true of total massive overhauls (e.g.,
>    if I were to rewrite doprnt.c [800+ lines of hacker byproduct] would
>    you still want it as a patch, or would you want my source file)?

Here's a rule of thumb: If the patch is bigger than the original
source, submit the new source.

> 3) Is there a design review procedure for bug-fixes & overhauls, or do we
>    just submit them when complete, and they get incorporated as is?

The standard is to submit patches to djgpp-workers AT delorie DOT com, where
the core djgpp developers can review it and incorporate it into djgpp.