Patches

Subject to the copyright assignment described below, your patches should be sent in git format-patch format relative to the current contents of the master branch of the Source Forge git repository. Please attach the output file or files generated by the git format-patch to the email rather than include them directory to avoid wrapping of the lines in the patch. Please be sure to use the Bacula indenting standard (see below) for source code. If you have checked out the source with git, you can get a diff using.

git pull
git format-patch -M

If you plan on doing significant development work over a period of time, after having your first patch reviewed and approved, you will be eligible for having developer git write access so that you can commit your changes directly to the git repository. To do so, you will need a userid on Source Forge.

Possible Next Steps

Go to Copyrights.

Go back to Developer Notes.

Go back to Developer Guide.