JD Harrington wrote: > Is there any documentation outlining the preferred process for patch > submission from members of the community? I've got something small I'd > like to send up, but I'm not entirely sure about where to send it > (misc@, bugs@/sendbug, or tech@) as it's not a bug, per se, and I'm also > not sure if there's a preference as to where in the src tree the patch > should be generated from. I've poked around the site and googled for > related list archives, but I can't seem to turn anything concrete up at > the moment. > > Thanks! > > -JD
diff -u. Non-unified diffs cause us to go blind. In-line, not attachment. Make sure your mailer doesn't mangle the diff or the spaces in it. i.e., mail it to yourself, see if you can apply it to a clean tree before you mail it to us. Odds are, your mailer will do something you don't expect, and we'll all laugh at you if you don't. If you are diffing one file, it probably doesn't matter much where you "root" the patch, at least if the patches we sling around internally are of any measure. If you are patching many files, I guess I prefer /usr/src as the root. If you get the rest of this right, we might be tollerant here. :) Including a usable unified diff pretty well qualifies you for posting to [EMAIL PROTECTED] It also enables you to give verbal beatings to those that don't. :)
