vim/vim-fugitive
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Place extra emphasis on a clean history

Browse Source
This commit is contained in:
Tim Pope 2014-03-05 15:17:49 -05:00
parent 0cb30541ec
commit 0765cbe466
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
CONTRIBUTING.markdown
View File

@ -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 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. them where I can, but it's up to you to isolate the conflict.
If your [commit message sucks](http://stopwritingramblingcommitmessages.com/), Fugitive is particularly prone to regressions due to Git version issues,
I'm not going to accept your pull request. I've explained very politely platform issues, and interactions with other plugins. I end up bisecting a
dozens of times that lot more than other projects, and thus I'm especially meticulous here about
[my general guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) maintaining a clean, readable, history. Squash and force push any requested
are absolute rules on my own repositories, so I may lack the energy to explain changes to a pull request. And if your [commit message
it to you yet another time. And please, if I ask you to change something, sucks](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
`git commit --amend`. I'm not going to accept it. Period.
Beyond that, don't be shy about asking before patching. What takes you hours 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 might take me minutes simply because I have both domain knowledge and a