aboutsummaryrefslogtreecommitdiff
path: root/.vim/bundle/vim-fugitive/CONTRIBUTING.markdown
diff options
context:
space:
mode:
authorxero <x@xero.nu>2014-05-05 15:09:26 -0400
committerxero <x@xero.nu>2014-05-05 15:09:26 -0400
commit89a2b67f2427d961bb2f0de771a0290d85e379f9 (patch)
treea30fa26360b7c3cf442689650da54865ac0f6fc3 /.vim/bundle/vim-fugitive/CONTRIBUTING.markdown
parent53b47ce8258f7efe380cc9dab09826b1f0e9bc27 (diff)
downloaddotfiles_ascii-89a2b67f2427d961bb2f0de771a0290d85e379f9.tar.xz
dotfiles_ascii-89a2b67f2427d961bb2f0de771a0290d85e379f9.zip
add vim configs -- yes i have joined the cult of vim
Diffstat (limited to '')
-rw-r--r--.vim/bundle/vim-fugitive/CONTRIBUTING.markdown18
1 files changed, 18 insertions, 0 deletions
diff --git a/.vim/bundle/vim-fugitive/CONTRIBUTING.markdown b/.vim/bundle/vim-fugitive/CONTRIBUTING.markdown
new file mode 100644
index 0000000..e651dca
--- /dev/null
+++ b/.vim/bundle/vim-fugitive/CONTRIBUTING.markdown
@@ -0,0 +1,18 @@
+Before reporting a bug, you should try stripping down your Vim configuration
+and removing other plugins. The sad truth about VimScript is that it is
+fraught with incompatibilities waiting to happen. I'm happy to work around
+them where I can, but it's up to you to isolate the conflict.
+
+Fugitive is particularly prone to regressions due to Git version issues,
+platform issues, and interactions with other plugins. I end up bisecting a
+lot more than other projects, and thus I'm especially meticulous here about
+maintaining a clean, readable, history. Squash and force push any requested
+changes to a pull request. And if your [commit message
+sucks](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
+I'm not going to accept it. Period.
+
+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 VimScript 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.