Git and development branch

This documentation is reserved for the developers which want to have their own distant branches to a Git repository. This techniques allow a better integration of new source for VLE or packages rather than sending patch to the integrator.

Initialization of local and distant repositories

 * We build a distant repository, called vle-dev (for example), into the $HOME/git directory, on a computer accessible with ssh:


 * On the local machine, we clone the default VLE repository (from Sourceforge) in read access only and we attach a new remote branch:

Send commits to the remote repository

 * Develop a lot of patchs on the local repository:

Synchronize your development with VLE official remote repository
In real life, you need to synchronise your local and remote repository to the VLE official repository.


 * First, you need to update the VLE official repository and merge your commits:

When a conflict occurs in the git rebase, follow the instruction and use git add [file] and git rebase --continue. When the conflicts are corrected, you need to send commits to your distant vle-dev repository.


 * To publish your new commits: