RTEMS GIT Repository

From RTEMSWiki
Jump to: navigation, search

Contents

RTEMS project's revision control tool is Git and the git repositories can be located at http://git.rtems.org/.

Why git?

Git is a distributed revision control system with an emphasis on speed and data safety. With git revision control system each user has a full featured copy of the main repository. Each revision control operation is done in the local repository and can be later shared using patches or by direct push to the main repository.

RTEMS Git Repositories

The RTEMS Git Repository contains the publicly maintained RTEMS code and personal developer repos at [1]

Bootstrapping RTEMS after a Git clone or pull

RTEMS uses Automake for Makefile generation (uses Makefile.am and preinstall.am files) and Autoconf for configuration (uses configure.ac files). Both tools generate files which are not contained in the Git repository. You need to generate them after a clone or pull. This file generation is performed by the bootstrap script in the top level RTEMS directory.

Bootstrap.png

RTEMS Git Server

RTEMS has a dedicated Git server. The machine runs cgit to provide a web interface to Git, the Git protocol for direct read-only access and ssh accounts for those with commit access. The configuration is standard with two hooks currently used to send commit details to the rtems-vc@rtems.org mailing list and to synchronize with the github mirrors.

Git Access for Users

The Git Users page has public read-only access instructions, some useful git commands, and directions on how to submit patches to RTEMS.

Git Access for Committers

The Git Committers page has policies and procedures for committers to make changes to the RTEMS repositories.

Git Commits

When committing a change the first line is a summary. Please make it short while hinting at the nature of the change. You can argument the change if you wish with a PR number. After the first line leave an empty line and add what ever required detail you feel is needed.

Please to not use terms such as "Fix bug" or "With this change it works". If you fix a bug please state the nature of the bug and why this change fixes it. If a change makes something work then detail the reason. You do not need to explain the change line by line as the commits diff will.

If you change formatting please make that a separate patch and use "Formatting changes only" on the first line.

Learn more about Git

Links to site with good Git information.

* http://gitready.com/ - an excellent resource from beginner to very advanced.
* http://progit.org/book/ - Covers git basics and some advanced features. Includes some useful workflow examples.
* http://gitref.org/ - Fast and simple reference for the most used git commands.
Personal tools
Namespaces

Variants
Actions
Navigation
Gedare's Special Help
Toolbox