Inhaltsverzeichnis

Pull UHSD source code from Github

Option: Download the zippd UHSDR

Option: Use "Github Desktop"

Option: Use "git" on command line level, command line style

A git cheat sheet can be found here

Fork UHSDR to your own remote github repo

Pull UHSDR from Github

Rebase: Synchronising your fork with UHSDR DF8OE repo

Creating branches for tests and experiments

Before creating any new branch please pull the changes from upstream as explained above. Make sure your forked repo is up to date.

Use local UHSDR clone in Eclipse

See also GNU MCU Eclipse workspace preferences

Option: Create work space
Option: Import UHSDR into eclipse

Contributing, Rebase

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.

Further reading

https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-clone http://www.ralfebert.de/git/