ChanServ changed the topic of #mlpack to: Due to ongoing spam on freenode, we've muted unregistered users. See http://www.mlpack.org/ircspam.txt for more information, or also you could join #mlpack-temp and chat there.
mentekid has quit [Ping timeout: 252 seconds]
caiocarvalho has joined #mlpack
caiocarvalho has quit [Ping timeout: 245 seconds]
Tufan has joined #mlpack
< Tufan>
help
Tufan has quit [Client Quit]
ImQ009 has joined #mlpack
ImQ009 has quit [Read error: Connection reset by peer]
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
robertohueso has quit [Read error: Connection reset by peer]
vivekp has quit [Ping timeout: 260 seconds]
vivekp has joined #mlpack
Hemal has joined #mlpack
< Hemal>
hello, i am trying to set up the development environment, so that i may be able to contribute.
< Hemal>
I feel that this was a wrong way to go further,
< Hemal>
I should have used github
< Hemal>
Like Cloning the repo, downloading project from there and then compiling from that source, adding a remote <<< is this a correct way to get the dev. environment ready ?
Hemal has quit [Quit: Leaving.]
Hemal has joined #mlpack
< rcurtin>
Hemal: I think everything you've done is fine, basically once you've configured the project with CMake and have it building you are ready to develop :)
< Hemal>
So if i make some changes, compile them using make, verify the them as working , i still need git repo to create a pull request , right ?
Hemal has quit [Quit: Leaving.]
Hemal has joined #mlpack
Hemal has left #mlpack []
< rcurtin>
ah, yeah, that is true
< rcurtin>
but if you've built mlpack 3.0.3 just fine the process will be the same for the git master branch
< rcurtin>
basically to contribute you'll need to fork the mlpack repository to your personal github account, check that one out, and make your changes there and push back to your personal fork