I slightly modified the subject line of the commits. To make it easier to see what's being changed maybe we should prefix the commit with the board affected. So for example I added "Odroid_XU4:" to the front of one of the commits.
By the way, I see your commits are coming from you repo's master branch. That's fine of course from my point of view but you may find it easier to keep your repo's master branch always synced with the diydrones/companion/master branch and then make PRs out of a new branch in your repo.
So for example, in my personal copy of companion I would use "remote add trunk https://github.com/diydrones/companion.git" then do "git fetch trunk", "git reset --hard trunk/master", "git push -f" to keep my repo's master in sync with upstream master. Then I'd do the "git branch -b example-feature1" to create a new branches to hold any new features I'm working on.
Up to you of course, and there are various ways to do it.. but this is what works for me.
merged, thanks!
I slightly modified the subject line of the commits. To make it easier to see what's being changed maybe we should prefix the commit with the board affected. So for example I added "Odroid_XU4:" to the front of one of the commits.
By the way, I see your commits are coming from you repo's master branch. That's fine of course from my point of view but you may find it easier to keep your repo's master branch always synced with the diydrones/companion/master branch and then make PRs out of a new branch in your repo. So for example, in my personal copy of companion I would use "remote add trunk https://github.com/diydrones/companion.git" then do "git fetch trunk", "git reset --hard trunk/master", "git push -f" to keep my repo's master in sync with upstream master. Then I'd do the "git branch -b example-feature1" to create a new branches to hold any new features I'm working on. Up to you of course, and there are various ways to do it.. but this is what works for me.