Version 52 (modified by ChrisJohns, on Jul 27, 2013 at 7:16:43 PM) (diff)

/* Git Access for Committers */

RTEMS GIT Repository

RTEMS project's revision control tool is Git and the git repositories can be located at

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 following modules are in the RTEMS GIT Repository and currently actively used for development. The complete list of available development modules can be found at

  • rtems.git - RTEMS Itself
  • Examples
    • examples-v2.git - RTEMS Examples (merges all other non-networked example collections)
    • network-demos.git - Example RTEMS Networking Programs
  • rtems-testing.git - Helpful scripts for testing. Includes Simulator Scripts, Coverage Testing help, git helpers, RTEMS testing, and GCC testing aids.
  • rtems-addon-packages.git - Free software libraries that have been ported to RTEMS including AVL, TCL, ncurses, readline, and zlib.
  • rtems-graphics-toolkit.git - Graphic support libraries for RTEMS.
  • rtems-schedsim-git - Scheduling Simulator

Bootstrapping RTEMS after a Git clone or pull

RTEMS uses Automake for Makefile generation (uses and files) and Autoconf for configuration (uses 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.

<center>No image "bootstrap.png" attached to Developer/Git</center>

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 the only hook currently used to send commit details to the rtems-vc@… mailing list.

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.

Attachments (1)

Download all attachments as: .zip