commit 0765cbe4668dbdedb6f5b9cb83642ea3f43b41fe (tree)
parent 0cb30541ec7e71b9558e164f100fe083ecd816c6
Author: Tim Pope <code@tpope.net>
Date: Wed, 5 Mar 2014 15:17:49 -0500
Place extra emphasis on a clean history
Diffstat:
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/CONTRIBUTING.markdown b/CONTRIBUTING.markdown
@@ -3,13 +3,13 @@ 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.
-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`.
+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
