+SBCL Style Guide
+
+ (This is not a most actively maintained file, but recommended
+ reading anyways.)
+
+Patch Submissions
+=================
+
+Preferred patch format is output from "git format-patch", including
+the commit message. The commit message should explain the why and how
+of the change.
+
+Please include test-cases in your patch if at all possible.
+
+Please format your submission for ease of reading: unless the change
+is whitespace only, avoid re-indenting code you are not touching, etc.
+Unless your patch is large and best understood as a series of
+sequential changes, please send it in as single patch file.
+
+If your patch includes algorithmic changes, explain them. If your
+patch uses a published algorithm, please include a link to the paper.
+We aren't always as well-educated as we'd like to...
+
+Ready-to-apply patches should be submitted via Launchpad: please add
+the tag "review" to the associated bug.
+
+Patches requiring more widespread discussion and feedback should be
+sent to the sbcl-devel mailing list.
+
+If you have any questions, feel free to ask them on sbcl-devel.
+
+Coding Style
+============
+
+See also PRINCIPLES and TLA files.
+