From: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization: Darmstadt University of Technology
To: "Alain Magloire" <alain AT qnx DOT com>
Date: Wed, 14 Feb 2001 09:37:39 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: [alain AT qnx DOT com: GNU_grep-2.5b_beta]
CC: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
In-reply-to: <200102140446.XAA17108@qnx.com>
References: <1E4DC52385A AT HRZ1 DOT hrz DOT tu-darmstadt DOT de> from "Juan Manuel Guerrero" at Feb 13, 2001 10:15:20 PM
X-mailer: Pegasus Mail for Windows (v2.54DE)
Message-ID: <1F03B5373FB@HRZ1.hrz.tu-darmstadt.de>
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

Date: Tue, 13 Feb 2001 23:46:00 -0500 (EST)
From: "Alain Magloire" <alain AT qnx DOT com>

> You did not provide a ChangeLog entry for your patch so I'll assume that
> the "From:" header field contain the right info for the THANKS and
> ChangeLog files.
Yes, the header info is ok.

> > on win95 using command.com and on msdos 6.22 using 4dos.com and
> > command.com. All targets worked ok after 2 bugs had been fixed.
> > 
> > The file djgpp/config.bat is broken, making configuration impossible
> > on msdos 6.22 if 4dos.com is used as shell. This has been fixed.
> 
> I do not have enough DOS knowledge to comment intelligently, so unless
> someone say otherwise,  I will apply the patch for config.bat.
As Eli pointed out, this is for 4DOS support on plain DOS.
It is the same stuff I have used in other DJGPP ports.


Date: Wed, 14 Feb 2001 09:15:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>

> > You did not provide a ChangeLog entry for your patch so I'll assume that
> > the "From:" header field contain the right info for the THANKS and
> > ChangeLog files.
>
> Juan, please try in the future to send a ChangeLog entry together with
> changes.  Some maintainers of GNU packages won't accept changes
> without a suitable ChangeLog entry.  The file standards.info includes
> a section on writing good ChangeLog entries.
Ok, next time.

Regards,
Juan Manuel Guerrero