mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dlyubi...@apache.org
Subject svn commit: r1597891 - /mahout/site/mahout_cms/trunk/content/developers/github.mdtext
Date Tue, 27 May 2014 22:06:34 GMT
Author: dlyubimov
Date: Tue May 27 22:06:33 2014
New Revision: 1597891

URL: http://svn.apache.org/r1597891
Log:
CMS commit to mahout by dlyubimov

Modified:
    mahout/site/mahout_cms/trunk/content/developers/github.mdtext

Modified: mahout/site/mahout_cms/trunk/content/developers/github.mdtext
URL: http://svn.apache.org/viewvc/mahout/site/mahout_cms/trunk/content/developers/github.mdtext?rev=1597891&r1=1597890&r2=1597891&view=diff
==============================================================================
--- mahout/site/mahout_cms/trunk/content/developers/github.mdtext (original)
+++ mahout/site/mahout_cms/trunk/content/developers/github.mdtext Tue May 27 22:06:33 2014
@@ -33,7 +33,7 @@ In this case it is recommended to squash
 than merging in a multitude of contributer's commits. In order to do that, as well as close
the PR at the 
 same time, it is recommended to use **squash commits**.
 
-Read [[2]] (merging locally). Merging pull requests are equivalent to merging contributor's
branch:
+Read \[[2]\] (merging locally). Merging pull requests are equivalent to merging contributor's
branch:
 
     git checkout master      # switch to local master branch
     git pull apache master   # fast-forward to current remote HEAD
@@ -59,7 +59,7 @@ Suppose everything is fine, you now can 
     git commit -a
 
 edit message to contain "MAHOUT-YYYY description **closes #ZZ**", where ZZ is the pull request
number. 
-Including "closes #ZZ" will close PR automatically. More information [[3]].
+Including "closes #ZZ" will close PR automatically. More information \[[3]\].
 
    push apache master
 
@@ -82,7 +82,7 @@ that should close PR without merging and
 
 ## Apache/github integration features 
 
-Read [[4]]. Issue handles mentioned in comments and PR name should post to mailing lists
and Jira.
+Read \[[4]\]. Issue handles mentioned in comments and PR name should post to mailing lists
and Jira.
 
 
 [1]: https://help.github.com/articles/creating-a-pull-request



Mime
View raw message