diff options
-rw-r--r-- | ChangeLog | 5 | ||||
-rw-r--r-- | doc/contributing.rdoc | 13 |
2 files changed, 15 insertions, 3 deletions
@@ -1,3 +1,8 @@ +Wed Jan 29 03:36:42 2014 Eric Wong <e@80x24.org> + + * doc/contributing.rdoc: allow/encourage other git hosts + [ruby-core:59807][misc #9421] + Tue Jan 28 23:36:01 2014 Tanaka Akira <akr@fsij.org> * ext/socket: Avoid redundant fcntl/fstat syscalls for cloexec diff --git a/doc/contributing.rdoc b/doc/contributing.rdoc index 9d9fbdf2da..c6ccc68302 100644 --- a/doc/contributing.rdoc +++ b/doc/contributing.rdoc @@ -436,7 +436,8 @@ your working branch: Now that you've got some code you want to contribute, let's get set up to generate a patch. Start by forking the github mirror, check the {github docs on forking}[https://help.github.com/articles/fork-a-repo] if you get stuck here. -here. You will also need a github account if you don't yet have one. +here. You will only need a github account if you intend to host your repository +on github. Next copy the writable url for your fork and add it as a git remote, replace "my_username" with your github account name: @@ -454,6 +455,12 @@ the patch for you, save the file to your computer and upload it to the bug tracker. Alternatively you can submit a pull request, but for the best chances to receive feedback add it is recommended you add it to redmine. - - +Since git is a distributed system, you are welcome to host your git repository +on any {publically accessible hosting +site}[https://git.wiki.kernel.org/index.php/GitHosting], including {hosting your +own}[https://www.kernel.org/pub/software/scm/git/docs/user-manual.html#public-repositories] +You may use the {'git format-patch'}[http://git-scm.com/docs/git-format-patch] +command to generate patch files to upload to redmine. You may also use +the {'git request-pull'}[http://git-scm.com/docs/git-request-pull] command for +formatting pull request messages to redmine. |