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."
Hemal has joined #mlpack
< Hemal>
Hello, i am a new member willing to contribute to MLpack, i would like to know, should i keep my local copy of MLpack repository, always up to date ? On GitHub, it shows, my forked copy is 33 commits behind the MLpack Master
Hemal has quit [Read error: Connection reset by peer]
< zoq>
Hemal: Usually, I update the master branch before I'll open a new PR.
< zoq>
davida: The model runs if I use a batch size of 1 instead of 32, have to take a closer look into the issue.
robertohueso has quit [Ping timeout: 252 seconds]
vivekp has quit [Read error: Connection reset by peer]
vivekp has joined #mlpack
Hemal has joined #mlpack
Hemal has left #mlpack []
Hemal has joined #mlpack
< Hemal>
zoq , just to clarify, you would make a local branch, perform some updates, then switch to master branch, then update master (from mlpack/mlpack), then merge the local branch(your changes), push to your github master and finally create a pull request?
< zoq>
Hemal: 1. Update own fork (master branch) 2. create a new feature branch (in the forked repo) make changes 3. create PR
Hemal has quit [Quit: Leaving.]
< zoq>
Hemal: Ideally I don't touch the master branch, I just sync it with the orginal master branch before I create a new branch.
Hemal has joined #mlpack
< Hemal>
ok so I can create a PR from my non-master branch for mlpack master branch ?
Hemal has left #mlpack []
Hemal has joined #mlpack
Hemal has left #mlpack []
< zoq>
Hemal: Yeah, at least that's the way I do it.