A git cheat sheet can be found here
$apt-get install git
$git clone https://github.com/DF9TS/UHSDR-1
git remote -v
git remote add upstream https://github.com/df8oe/UHSDR
git pull --rebase upstream active-devel
git push origin active-devel
Before creating any new branch please pull the changes from upstream as explained above. Make sure your forked repo is up to date.
$ git checkout -b [name_of_your_new_branch]
$ git checkout [name_of_your_new_branch]
$ git push origin [name_of_your_new_branch]
$ git branch
$ git remote add [name_of_your_remote]
$ git push [name_of_your_new_remote] [name_of_your_branch]
$ git fetch [name_of_your_remote]
$ git merge [name_of_your_remote]/develop
$ git branch -d [name_of_your_new_branch]
$ git branch -D [name_of_your_new_branch]
$ git push origin :[name_of_your_new_branch]
See also GNU MCU Eclipse workspace preferences
The heart of any open source project is the contributions by individuals. Source code for the project is using git currently and can be found here. There is a good explanation of github workflow here that is worth a read before branching and hacking on the code. And an online book written directly from the git creators you can find here - or locally here.
We have specific instructions for contributors collected in guidelines for contributing.
For own developments and experiments in code you should NOT use merge/pull to integrate your changes in df8oe's active-devel. Instead use git “rebase” command, as documented on our contribution page. We had very little trouble to follow that approach for the last two years. It also has its issues but in general, once you understand how to operate it, it works quite well. The main benefit of the rebase approach is that it keeps all your “local” changes together on top of the last official release you rebased on. Opposed to the merge approach you have been running, which does mingle your changes with the external changes in the time history.