aboutsummaryrefslogtreecommitdiff
path: root/vim/3rdparty/vim-pathogen/CONTRIBUTING.markdown
diff options
context:
space:
mode:
Diffstat (limited to 'vim/3rdparty/vim-pathogen/CONTRIBUTING.markdown')
m---------vim/3rdparty/vim-pathogen0
-rw-r--r--vim/3rdparty/vim-pathogen/CONTRIBUTING.markdown14
2 files changed, 0 insertions, 14 deletions
diff --git a/vim/3rdparty/vim-pathogen b/vim/3rdparty/vim-pathogen
new file mode 160000
+Subproject 8c91196cfd9c8fe619f35fac6f2ac81be10677f
diff --git a/vim/3rdparty/vim-pathogen/CONTRIBUTING.markdown b/vim/3rdparty/vim-pathogen/CONTRIBUTING.markdown
deleted file mode 100644
index f5a62ca..0000000
--- a/vim/3rdparty/vim-pathogen/CONTRIBUTING.markdown
+++ /dev/null
@@ -1,14 +0,0 @@
-If your [commit message sucks](http://stopwritingramblingcommitmessages.com/),
-I'm not going to accept your pull request. I've explained very politely
-dozens of times that
-[my general guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
-are absolute rules on my own repositories, so I may lack the energy to
-explain it to you yet another time. And please, if I ask you to change
-something, `git commit --amend`.
-
-Beyond that, don't be shy about asking before patching. What takes you
-hours might take me minutes simply because I have both domain knowledge
-and a perverse knowledge of Vim script so vast that many would consider
-it a symptom of mental illness. On the flip side, some ideas I'll
-reject no matter how good the implementation is. "Send a patch" is an
-edge case answer in my book.