Mar 14, 1995, 12:03 PM
Post #4 of 4
>> Yes, and can we start prepending GNU-style ChangeLog entries to the patches?
>Can you please explain this for those of us who don't know about this
Sorry, here is an example:
Sun Sep 4 00:35:24 1994 Richard Stallman <firstname.lastname@example.org>
* s/linux.h (LD_SWITCH_SYSTEM): Definition deleted.
* m/hp9000s300.h [not BSD4_3] [__GNUC__] (HAVE_ALLOCA): Defined.
* xfns.c (defined_color): New arg ALLOC--optionally don't allocate
(x_decode_color, Fx_color_defined_p): Pass new arg.
(Fx_color_values): New function.
* sysdep.c (random, srandom): Check HAVE_LRAND48, not HAVE_RAND48.
Call lrand48, nor rand48.
* window.c (window_loop, case UNSHOW_BUFFER):
When we delete a frame, skip all the windows on that frame.
Fri Aug 12 19:11:43 1994 Karl Heuer <email@example.com>
* s/isc4-0.h (NEED_SIOCTL): moved to isc-3.0.h.
Each source file is listed separately. Before the change description is
some identification of where the change was made; typically this is
the name of the routine in paranetheses, but case statement labels and
#if tests can also be given.
If you are editing a source file using emacs, then C-x 4 a will start
a changelog entry for the routine that the cursor is in.
Patches should be supplied prepended with the change log entry; when you
apply the patch, you prepend the entry to the ChangeLog file in the source
directory. (By hand, I think.)
Thus you can search the ChangeLog for changes to a particular routine or