How we handle patches (mmoved): Difference between revisions

# Before creating the patch, update the master branch of your local repository checkout, and make sure your commits apply cleanly on top of master. In git, you can achieve this by [http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html#_managing_branches developing on a branch] and rebasing your branch commits on top of master with <code>[http://www.kernel.org/pub/software/scm/git/docs/git-rebase.html git rebase master]</code>. You can also use <code>git rebase -i master</code> for an interactive rebase, in which you can reorder and edit commits. We prefer rebasing to merging because rebasing preserves a linear commit history, which can be easier to keep track of and reason about.

# Generate the patch set for your changes. Our preferred patch submission form is a patch series generated with "git format-patch". Read about [[How to generate patches with git format-patch]]. Add on a line of its own, at the bottom of the commit, what the patch fixes. For example: "Closes: http://openhatch.org/bugs/issue398"

 

=== Permit us to share your work: ===