Date: Wed, 15 Oct 1997 13:29:24 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Thomas Demmer <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De>
cc: djgpp AT delorie DOT com
Subject: Re: ANNOUNCE: libc patch site
In-Reply-To: <34433BC2.71885E82@LSTM.Ruhr-UNI-Bochum.De>
Message-ID: <Pine.SUN.3.91.971015132900.17868Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 14 Oct 1997, Thomas Demmer wrote:

> and install the sources under /djgpp/src.
> unzip the required patchfile.
> Type
>  patch < ptfXXXX.pat

I suggest saying "patch -p0 < ptfXXXX.pat" instead.  Most of the patch
files won't work automatically otherwise (you'll get a prompt from
`patch' asking which file to patch).

> Make a context diff against the old stock source. Put this into 
> ptfXXXX.pat, where the XXXX is replaced by the bug number. 

For those who don't know: context diffs are generated by the `diff'
program (from GNU Diffutils, get v2gnu/dif271b.zip), with this
command:

	diff -c old new
or
	diff -u old new

(-c and -u generate the diffs in different formats, but `patch'
understands both; the output of -c is somewhat larger.)

But the important thing is TO PUT THE OLD VERSION FIRST on the command
line!  Otherwise, your diff will be backwards.

> The path should start relative to /djgpp/src.

I suggest to make it relative to the root of the DJGPP installation.
That is how DJ Delorie asks the patches to be done.  If the same rule
is preserved on this site, people won't need to create their patches
twice.

Please use RELATIVE pathnames of the sources when you type the `diff'
command line.  This will allow anybody to apply the patch
automatically, even if their top-level DJGPP directory is different.

For example, here's how to create a patch for the `read.c' module:

 cd c:\djgpp
 diff -c src/libc/posix/unistd/read.bak src/libc/posix/unistd/read.c > read.pat

(this assumes that DJGPP is installed in C:\DJGPP).