Before you do
Before making a patch you should do the following:
- Check that modified documents are well-formed and valid.
- Spell check using American English.
- Check that the book is valid.
- Build the document and check the output for technical and linguistic problems.
Make a Patch
Preparing a patch is easy. You can make a patch for a single file or a group of files that have been modified.
To create a patch for a group of files:
- Change the present working directory to the root of your working copy.
Issue the svn update command.
This updates your working copy with changes from the repository. Check for conflicts and resolve them.
Issue the svn status command.
This shows the status of files. Ensure that all conflicts are resolved.
Issue the command svn diff > diffname.txt
This creates the file "diffname.txt," which contains the differences between the working copy and repository revisions of the modified files.
To create a patch for specific file:
- Change the present working directory to the directory containing the modified file.
Issue the svn update filename.xml command.
This updates the specific working copy file with changes from the repository. Check for conflicts and resolve them.
Issue the command svn diff workingfile.xml > filename.xml.diff
This creates the file "filename.xml.diff," which contains the differences between the working copy and repository revisions of the modified file.
For more information about working with SVN, see Version Control with Subversion.
Submitting a Patch
With the exception of comitters, all patches are submitted through our issue tracker as attachments to an issue ticket. Please do not post attachments to the mail list. A comitter with permissions will apply the patch after testing. If the patch has special testing requirements, attach a file that enables testing and/or explain how to test.