Compare commits

..

No commits in common. "d7ccd86c677ca5de9a583fff3f04edf37a28c39c" and "e53bd31bb75fb69f1000c245d1c67e01ff4b59e6" have entirely different histories.

View file

@ -10,6 +10,6 @@ If you want to contribute, you can submit a topic for a new issue for a reposito
Send an email to [issue@seodisparate.com](mailto:issue@seodisparate.com) with details for an issue for a specific repository and I will make an issue for the repository for your request. Send an email to [issue@seodisparate.com](mailto:issue@seodisparate.com) with details for an issue for a specific repository and I will make an issue for the repository for your request.
Send an email to [pull\_req@seodisparate.com](mailto:pull_req@seodisparate.com) with patches sent with [git send-email](https://git-scm.com/docs/git-send-email) and/or [git format-patch](https://git-scm.com/docs/git-format-patch) and I will make a pull request with your patches and review them. (Be sure to mention the repository you want to contribute to! You can do this by mentioning the repo in the cover letter with option `--cover-letter` like so: `git format-patch --cover-letter ...`.) Send an email to [pull\_req@seodisparate.com](mailto:pull_req@seodisparate.com) with patches sent with [git send-email](https://git-scm.com/docs/git-send-email) and/or [git format-patch](https://git-scm.com/docs/git-format-patch) and I will make a pull request with your patches and review them.
Since email hosted by my website is "self-hosted", emails from my website may end up in a spam folder, so if you expect a reply, be wary of this. Since email hosted by my website is "self-hosted", emails from my website may end up in a spam folder, so if you expect a reply, be wary of this.