[
https://issues.apache.org/jira/browse/MAHOUT-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151877#comment-13151877
]
[email protected] commented on MAHOUT-888:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2872/
-----------------------------------------------------------
Review request for mahout.
Summary
-------
This diff is just of the README.txt, formatting it so that all lines are 80
characters or less, as an example diff for MAHOUT-888
This addresses bug MAHOUT-888.
https://issues.apache.org/jira/browse/MAHOUT-888
Diffs
-----
trunk/README.txt 1203081
Diff: https://reviews.apache.org/r/2872/diff
Testing
-------
No code was changed, so no testing was done!
Thanks,
Jake
> Start using newly acquired reviewboard instance!
> ------------------------------------------------
>
> Key: MAHOUT-888
> URL: https://issues.apache.org/jira/browse/MAHOUT-888
> Project: Mahout
> Issue Type: Wish
> Affects Versions: 0.6
> Reporter: Jake Mannix
> Priority: Minor
> Fix For: 0.6
>
>
> It's easy: go to https://reviews.apache.org/ and submit a review by clicking
> "new review request", then picking the project to be "mahout", base directory
> to be "trunk", and upload your patch. Add "mahout" to the reviewer group of
> your reviewboard, pick some people you want to aim the review at (if you
> think you know the "owner" of the code area you're hitting), set the "bug
> number" in the appropriate field so that JIRA and RB will magically
> communicate, and don't forget to click the "publish" button when you're ready
> for people to look at it. You can also look at your review directly for
> sanity checking before doing so by clicking on the "view diff" button.
> ReviewBoard can be slow and clunky, but inline comments in the diff are A+
> goodness.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
