2000-12-10 -+- Karl M. Hegbloom -+- karlheg@debian.org -+- A bug report that includes a patch is an especially valuable<br>contribution!  If you enjoy puzzles, believe you know how to fix the<br>problem, and have some time on your hands, then by all means...<br><br>(first making sure you've got "deb-src" lines in "/etc/apt/sources.list")<br>  # apt-get update<br><br>  % cd &lt;srcdir&gt;<br>  % mkdir &lt;pkgname&gt;<br>  % cd &lt;pkgname&gt;<br>  % apt-get source &lt;pkgname&gt;<br><br>I recommend using RCS to assist in generating the patch.  Check it in<br>before you begin, and use it to create a "-u" diff to paste into the<br>bug report, along with a decently detailed change description.  Please<br>include a summary paragraph and perhaps a rationale if the<br>modifications are relatively extensive and need explanation to<br>convince people the patch is necessary.  Don't forget to mention what<br>bug(s) it fixes.  If you plan to do a lot of work, it's best to<br>communicate with the maintainer, to avoid duplication of effort.  Log<br>your changes as you go, so you don't have to dig through the patch to<br>construct your ChangeLog.<br>