Oh, sorry, I just realized you're in the website subversion repo. For that you could attach an actual diff/patch file to the JIRA ticket and someone will take it on to apply.
So for the diff you created you could redirect it to a patch called MAHOUT-1874.patch for instance by doing `git diff > MAHOUT-1874.patch` in a simple case, and then upload to the JIRA ticket. If you're working in a branch it will be `git diff master > MAHOUT-1874.patch`. On Sat, Aug 27, 2016 at 8:45 PM, Andrew Musselman < [email protected]> wrote: > As I recall you'll want to go to https://github.com/apache/mahout and > "fork" it using the button in the top right (when you're logged into > github), then clone from your own forked version. > > Then after you make changes you'll check them in and push them to your own > version, then go back to your forked version in github and make your pull > request from there; here's a tutorial: https://help.github. > com/articles/creating-a-pull-request > > Hope this helps, let us know if you get stuck and we'll be happy to help. > > On Sat, Aug 27, 2016 at 8:31 PM, Sanjeev Kumar <[email protected]> wrote: > >> I guess, I would need some help:D >> >> So, I checked out the code locally and made the change. Attached a >> screenshot in jira, now how to create a PR. PR is pull request I guess. >> >> Thanks >> >> On Sun, Aug 28, 2016 at 8:36 AM, Suneel Marthi <[email protected]> >> wrote: >> >> > Nope, u just submit a PR against this jira with ur fix. Let us know if >> u >> > need help. >> > >> > On Sat, Aug 27, 2016 at 11:04 PM, Sanjeev Kumar <[email protected]> >> wrote: >> > >> > > Do I need to open a new jira issue to become a committer at mahout? >> > > >> > > On Sun, Aug 28, 2016 at 8:25 AM, Andrew Palumbo <[email protected]> >> > > wrote: >> > > >> > > > Welcome Sanjeev, >> > > > Please do go ahead and fix it. You'll need to create a diff and >> attach >> > > it >> > > > to that jira. >> > > > Thanks, >> > > > Andy >> > > > >> > > > >> > > > >> > > > -------- Original message -------- >> > > > From: "Sanjeev Kumar (JIRA)" <[email protected]> >> > > > Date: 08/27/2016 22:13 (GMT-05:00) >> > > > To: [email protected] >> > > > Subject: [jira] [Commented] (MAHOUT-1874) Broken markdown in >> Downloads >> > > > section on Mahout site >> > > > >> > > > >> > > > [ https://issues.apache.org/jira/browse/MAHOUT-1874?page= >> > > > com.atlassian.jira.plugin.system.issuetabpanels:comment- >> > > > tabpanel&focusedCommentId=15442579#comment-15442579 ] >> > > > >> > > > Sanjeev Kumar commented on MAHOUT-1874: >> > > > --------------------------------------- >> > > > >> > > > Well, I'm new here...just starting off. Can I take this over, to >> get a >> > > > feel of the process of contributing? >> > > > >> > > > Thanks >> > > > >> > > > > Broken markdown in Downloads section on Mahout site >> > > > > --------------------------------------------------- >> > > > > >> > > > > Key: MAHOUT-1874 >> > > > > URL: https://issues.apache.org/ >> > jira/browse/MAHOUT-1874 >> > > > > Project: Mahout >> > > > > Issue Type: Documentation >> > > > > Components: Documentation >> > > > > Reporter: Kyriakos Georgiou >> > > > > Priority: Trivial >> > > > > Labels: Documentation, Markdown, Site >> > > > > Original Estimate: 5m >> > > > > Remaining Estimate: 5m >> > > > > >> > > > > There's a space that breaks the closing back-ticks around >> > > > ```~/.bash_profile`` ` at https://svn.apache.org/viewvc/ >> > > > mahout/site/mahout_cms/trunk/content/general/downloads. >> > > > mdtext?view=markup#l22 >> > > > >> > > > >> > > > >> > > > -- >> > > > This message was sent by Atlassian JIRA >> > > > (v6.3.4#6332) >> > > > >> > > >> > >> > >
