|
From: Francois B. <ig...@gm...> - 2014-05-21 12:25:26
|
Hi, Excuse me for going a bit off-topic. I'd like to contribute some changes, but being new to git, I'm unsure how to progress. I've forked the quantlib repo, and cloned it. I've created a new branch to work on. Everything is still clean. Now, I first have to modify my .vcxproj files to point to my own boost installation. Obviously these are changes that I don't want to include in the pull request later. After adding boost and checking that it compiles correctly, I do a commit. Now I'm ready to start with the actual work. Let's assume I've finished that and do another commit. How do I proceed now? I want to create a pull request, but I don't know how to exclude the original, irrelevant commits. Is this easily possible? Should I use git rebase or have used multiple branches? I also posed this question on http://stackoverflow.com/questions/23781928/git-ignore-first-few-changes Once I figure this out, I want to apply a similar technique to pull in the outstanding commits from Peter's changes (to let the QuantlibAddin build successfully) and then do some work to expose more functions for the AddIn. Yet again, I'll have to create a pull request, but I want to exclude Peter's changes, because those are already in a pull request. Sorry for the newbie questions, but I hope you'll appreciate the contributions that I can make. regards Francois Botha |