Mailing List Archive: Apache: Dev

apache-pre.tar.Z - remove patch.status_302

Index | Next | Previous | View Threaded

hartill at ooo

Mar 13, 1995, 11:16 AM

Post #1 of 4 (134 views)
Permalink

apache-pre.tar.Z - remove patch.status_302

patch.status_302

needs to be removed from apache-pre.tar.Z and replaced with B18,
and B18 needs to be tested (it seems to work ok)

Can we please use the numbering scheme to store the patches, as
well as to document them. It makes life much easier if you
can look at the new code and see that it refers to a particular
patch number.

rob h

hartill at ooo

Mar 13, 1995, 12:30 PM

Post #2 of 4 (131 views)
Permalink

Re: apache-pre.tar.Z - remove patch.status_302 [In reply to]

>
> >Can we please use the numbering scheme to store the patches, as
> >well as to document them. It makes life much easier if you
> >can look at the new code and see that it refers to a particular
> >patch number.
>
> Yes, and can we start prepending GNU-style ChangeLog entries to the patches?
> Having a changelog makes it easier to remember who did what.

Can you please explain this for those of us who don't know about this
system.

rob

drtr at ast

Mar 13, 1995, 6:24 PM

Post #3 of 4 (131 views)
Permalink

Re: apache-pre.tar.Z - remove patch.status_302 [In reply to]

>Can we please use the numbering scheme to store the patches, as
>well as to document them. It makes life much easier if you
>can look at the new code and see that it refers to a particular
>patch number.

Yes, and can we start prepending GNU-style ChangeLog entries to the patches?
Having a changelog makes it easier to remember who did what.

David.

drtr at ast

Mar 14, 1995, 12:03 PM

Post #4 of 4 (136 views)
Permalink

Re: apache-pre.tar.Z - remove patch.status_302 [In reply to]

Rob wrote:
>> 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
>system.

Sorry, here is an example:
-----
Sun Sep 4 00:35:24 1994 Richard Stallman <rms [at] mole>

* 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
the color.
(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 <kwzh [at] hal>

* 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
source file.

David.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads