diff --git a/Documenation/SubmittingPatches.md b/Documenation/SubmittingPatches.md
index 1d28a9c52..1acca0396 100644
--- a/Documenation/SubmittingPatches.md
+++ b/Documenation/SubmittingPatches.md
@@ -4,12 +4,6 @@ to this repository.
 Make separate commits for logically separate changes.
 =====================================================
 
-Unless your patch is really trivial, you should not be sending
-out a patch that was generated between your working tree and
-your commit head.  Instead, always make a commit with complete
-commit message and generate a series of patches from your
-repository.  It is a good discipline.
-
 Give an explanation for the change(s) that is detailed enough so
 that people can judge if it is good thing to do, without reading
 the actual patch text to determine how well the code does what
@@ -25,33 +19,6 @@ change, the approach taken by the change, and if relevant how this
 differs substantially from the prior version, are all good things
 to have.
 
-Make sure that you have tests for the bug you are fixing.  See
-t/README for guidance.
-
-When adding a new feature, make sure that you have new tests to show
-the feature triggers the new behavior when it should, and to show the
-feature does not trigger when it shouldn't.  After any code change, make
-sure that the entire test suite passes.
-
-If you have an account at GitHub (and you can get one for free to work
-on open source projects), you can use their Travis CI integration to
-test your changes on Linux, Mac (and hopefully soon Windows).  See
-GitHub-Travis CI hints section for details.
-
-Do not forget to update the documentation to describe the updated
-behavior and make sure that the resulting documentation set formats
-well. It is currently a liberal mixture of US and UK English norms for
-spelling and grammar, which is somewhat unfortunate.  A huge patch that
-touches the files all over the place only to correct the inconsistency
-is not welcome, though.  Potential clashes with other changes that can
-result from such a patch are not worth it.  We prefer to gradually
-reconcile the inconsistencies in favor of US English, with small and
-easily digestible patches, as a side effect of doing some other real
-work in the vicinity (e.g. rewriting a paragraph for clarity, while
-turning en_UK spelling to en_US).  Obvious typographical fixes are much
-more welcomed ("teh -> "the"), preferably submitted as independent
-patches separate from other documentation changes.
-
 Oh, another thing.  We are picky about whitespaces.  Make sure your
 changes do not trigger errors with the sample pre-commit hook shipped
 in templates/hooks--pre-commit.  To help ensure this does not happen,