Libav is developed using Git as source management software. This page document the specific workflow and the tools available.
Libav uses a linear Git tree, that means that:
There are no merge points and only branch points from master to release branches.
The main mean to backport from master to release fixes is the cherry-pick.
The code remains easy to bisect and rebase actions are straightforward.
Every developed is advised to develop topic branches and keep them fresh using interactive rebase over the master tree.
The code will be tested using Oracle during review.
In general sending patches to review is as simple as calling git send-email origin --to firstname.lastname@example.org from the topic branch.
Currently the patch tracker patchwork is used to access the pending patches in a simplified way.
During the review process changes might be requested or alternate patches might be proposed. The GitAlias cover some quick means to fetch the patches from patchwork and again git rebase -i is a boon to keep the set in shape.