OpenHatch git workflow

Some guidelines on how to use git when working on OpenHatch

= Getting a new clone of OpenHatch = Only need to do this once. Or if you want to start form scratch. It is also good (okay) to remove your  directory and start over if you aren't sure the state of your OpenHatch repository.

= Committing a patch =
 * 1) After you have already retreived your respository of code. And you have made some changes, now you need to submit your patch (that will contain your changes) for review to OpenHatch.
 * 2)  (opens in less editor)
 * 3) Now git any updates that may have occurred since you last did a  or a
 * 1)  (opens in less editor)
 * 2) Now git any updates that may have occurred since you last did a  or a
 * 1) Now git any updates that may have occurred since you last did a  or a
 * 1) Now git any updates that may have occurred since you last did a  or a

Note: The  and   commands aren't modifying your patch, these commands are run to track your changes, and see what state your patch is in, in comparison to the origin

= Submitting a patch = Find your patch file that has been generated from the  command. In your current directory you can run which will list your files in time-sort order. Listing the newest modified files at the bottom. Look for the file similar to . This file or these files will need to be added to the bug tracker... if we are still doing this. The alternative is just using github, which some people are starting to look into.

= Other useful commands =
 * -- to combine patches into one. after which re-run format-patch command. notice "-i"

= Resources =
 * http://help.github.com/git-cheat-sheets/

= See also =
 * How to generate patches with git format-patch
 * How we handle patches