71 lines
2.8 KiB
HTML
71 lines
2.8 KiB
HTML
<html><head><title>
|
|
Patching Procedures
|
|
</title></head><body><h3>
|
|
Patching Procedures
|
|
</h3>
|
|
|
|
<IMG align=left SRC=pic/rabbit.gif>From <i>pogo</i>, Walt Kelly
|
|
<br clear=left><hr>
|
|
|
|
<p>A distribution so widely used as this one eventually develops
|
|
numerous barnacles as the result of <a href=porting.htm>porting</a>
|
|
to new systems, idiosyncratic new features and just plain bugs. In order
|
|
to help keep order and make maintenance bearable, we ask that proposed
|
|
changes to the distribution be submitted in the following form.
|
|
|
|
<ol>
|
|
|
|
<p><li>Please submit patches to <a href=mailto:mills@udel.edu>David L.
|
|
Mills <mills@udel.edu></a> in the form of either unified-diffs
|
|
(<tt>diff -u</tt>) or context-diffs (<tt>diff -c</tt>).</li>
|
|
|
|
<p><li>Please include the <strong>output</strong> from
|
|
<tt>config.guess</tt> in the description of your patch. If
|
|
<tt>config.guess</tt> does not produce any output for your machine,
|
|
please fix that, too!</li>
|
|
|
|
<p><li>Please base the patch on the root directory of the distribution.
|
|
The preferred procedure here is to copy your patch to the root directory
|
|
and mumble</li>
|
|
|
|
<p><tt>patch -p <your_patch></tt></li>
|
|
|
|
<p><li>Please avoid patching the RCS subdirectories; better yet, clean
|
|
them out before submitting patches.</li>
|
|
|
|
<p><li>If you have whole new files, as well as patches, wrap the files
|
|
and patches in a shell script. If you need to compress it, use either
|
|
GNU zip or the stock Unix compress utility.</li>
|
|
|
|
<p><li>Don't forget the documentation that may be affected by the patch.
|
|
Send us patches for the <tt>./html</tt> files as well. See the <a
|
|
href=htmlprimer.htm>A Beginner's Guide to HTML</a> page for a
|
|
tutorial.</li>
|
|
|
|
<p><li>We would be glad to include your name, electric address and
|
|
descriptive phrase in the <a href=copyright.htm>Copyright</a> page,
|
|
if you wish.</li>
|
|
|
|
</ol>
|
|
|
|
<p>Prior to ntp3-5.83 (releases up to and including ntp3.5f) a
|
|
complete patch history back to the dark ages was kept in the
|
|
<tt>./patches</tt> directory, which might have been helpful to see
|
|
if the same problem occured in another port, etc. Patches were saved in
|
|
that directory with file name in the form <tt>patch.<i>nnn</i></tt>,
|
|
where <i>nnn</i> was approaching 200. All patches in that directory have
|
|
been made; so, if yours was there, it was in the distribution.
|
|
|
|
<p>Since we have been getting multple patches for some bugs, plus many
|
|
changes are implemented locally, no two maintainers here use the same
|
|
tools, and since we're not using any bug-tracking software or even
|
|
source code control, there is currently no tracking of specific changes.
|
|
|
|
<p>The best way to see what's changed between two distributions is to
|
|
run a <tt>diff</tt> against them.
|
|
<p>Thanks for your contribution and happy chime.
|
|
|
|
<hr><a href=index.htm><img align=left src=pic/home.gif></a><address><a
|
|
href=mailto:mills@udel.edu> David L. Mills <mills@udel.edu></a>
|
|
</address></a></body></html>
|