Openbox

Wiki

Introduction
Screen Shots
Contributors
Platforms
Mailing Lists
Downloads
Bug Reports

Changelogs

Stable
Testing

Documentation

Whats new
Using Openbox

F.A.Q.
Openbox Features
Epist Features
Docker
The RC File
Menu File

Submitting a patch
What to do about a bug

Follow these directions to submit a patch:

  • First, you need to get a copy of the latest source code via cvs. Instructions for doing this can be found here.
  • Once you have a current copy of the source code, edit the code to make it do what you want it to do, or to fix a bug, etc.
  • Test your edited version of Openbox. Test it again. Test it again.
  • Once you are sure that it is working how you want to it work, you need to create the patch. First, make sure that you capture any changes to the cvs repository since you got you copy of the code. This can be done by going to the top level of the openbox code, and using the command

    cvs update -dAP

  • Now, to make the patch which you will be submitting, use the command

    cvs diff -puRN > yourchanges.patch

  • Now you should take a look at this patch. Looking at what you changed is a good way to find bugs in your code. Once you are satisfied with the patch, mail it to us.