Repository: mahout Updated Branches: refs/heads/master c29496cb1 -> 31833fa68
WEBSITE Typos and grammar closes apache/mahout#320 Project: http://git-wip-us.apache.org/repos/asf/mahout/repo Commit: http://git-wip-us.apache.org/repos/asf/mahout/commit/31833fa6 Tree: http://git-wip-us.apache.org/repos/asf/mahout/tree/31833fa6 Diff: http://git-wip-us.apache.org/repos/asf/mahout/diff/31833fa6 Branch: refs/heads/master Commit: 31833fa6827729155934be77bdde7c546ebd47f3 Parents: c29496c Author: Bruno P. Kinoshita <[email protected]> Authored: Sat May 20 22:44:04 2017 -0500 Committer: rawkintrevo <[email protected]> Committed: Sat May 20 22:44:04 2017 -0500 ---------------------------------------------------------------------- website/oldsite/developers/github.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mahout/blob/31833fa6/website/oldsite/developers/github.md ---------------------------------------------------------------------- diff --git a/website/oldsite/developers/github.md b/website/oldsite/developers/github.md index 24a4aa8..61a373d 100644 --- a/website/oldsite/developers/github.md +++ b/website/oldsite/developers/github.md @@ -13,7 +13,7 @@ Apache and various policies there make backing out mistakes problematic. Therefo go through a PR, even for committers. To keep the commit history clean take note of the use of --squash below when merging into apache/master. -##Git setup for Committers +## Git setup for Committers This describes setup for one local repo and two remotes. It allows you to push the code on your machine to either your Github repo or to git-wip-us.apache.org. You will want to fork github's apache/mahout to your own account on github, this will enable Pull Requests of your own. @@ -44,7 +44,7 @@ Now if you want to experiment with a branch everything, by default, points to yo Once you are ready to commit to the apache remote you can merge and push them directly or better yet create a PR. -##How to create a PR (committers) +## How to create a PR (committers) Push your branch to Github: @@ -141,7 +141,7 @@ that should close PR `ZZ` on github mirror without merging and any code modifica ## Apache/github integration features Read \[[4]\]. Comments and PRs with Mahout issue handles should post to mailing lists and Jira. -Mahout issue handles must in the form MAHOUT-YYYYY (all capitals). Usually it makes sense to +Mahout issue handles must be in the form MAHOUT-YYYYY (all capitals). Usually it makes sense to file a jira issue first, and then create a PR with description MAHOUT-YYYY: <jira-issue-description> @@ -154,4 +154,4 @@ jira issue explicitly in each comment of the PR. [1]: https://help.github.com/articles/creating-a-pull-request [2]: https://help.github.com/articles/merging-a-pull-request#merging-locally [3]: https://help.github.com/articles/closing-issues-via-commit-messages -[4]: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and \ No newline at end of file +[4]: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
