]> git.madduck.net Git - etc/vim.git/blobdiff - .vim/bundle/vim-pathogen/CONTRIBUTING.markdown

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

projects / etc / vim.git / blobdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | inline | side by side
Merge commit '55bf04470ecc026e71c037f0f35402fdeac66767' as '.vim/bundle/vim-pathogen'
[etc/vim.git] / .vim / bundle / vim-pathogen / CONTRIBUTING.markdown
diff --git a/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown b/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown
new file mode 100644 (file)
index 0000000..3bbabf8
--- /dev/null
+++ b/.vim/bundle/vim-pathogen/CONTRIBUTING.markdown
@@ -0,0 +1,18 @@
+Follow the commit message guidelines at [commit.style](https://commit.style).
+This is an absolute requirement for my repositories, and doing so proves you
+actually read the contribution guidelines, which makes for a good first
+impression.
+
+Good commit messages imply good commits.  Pull requests should typically be a
+single commit, or for the rare complicated case, a series of atomic commits.
+If I request a change, use `git commit --amend` or `git rebase --interactive`
+and force push to your branch.
+
+For feature requests, don't be shy about proposing it in an issue before
+drafting a patch.  If it's a great idea, I might do it for you.  If it's a
+terrible idea, no patch will change my mind.
+
+The worst ideas are configuration options.  You'll need to provide a great
+justification in order to persuade me to take on the maintenance and support
+burden it will inevitably entail.  See if you can get away with a custom map
+or autocommand instead.
vim configuration

Legalese

All content available in this repository is copyright © martin f. krafft, unless otherwise noted.

All files and their content are released under the terms of the Artistic Licence 2.0, unless otherwise noted.

The operator of this repository shall not be held liable for offending content in pages linking to or linked from these page, nor does he endorse their content unless stated otherwise.