gawkworkflow: Developing patches

1 
1 5.3 Developing Patches
1 ======================
1 
1 The first part of developing a patch is the same as for developers
1 without commit access:
1 
1   1. Develop the code and test it.
1 
1   2. Update the 'ChangeLog'.
1 
1   3. If necessary, update the documentation: 'doc/gawktexi.in' and/or
1      'doc/gawk.1'.
1 
1   4. Use 'git diff > mychange.diff' to create a patch file.
1 
1   5. Send it to the mailing list for discussion.
1 
1   6. Iterate until the patch is ready to be committed.
1 
1    However, now that you have commit access, you can commit the fix and
1 push it up to the repo yourself!  Let's assume you've made a bug fix
1 directly on 'master'.  Here's how to commit your changes:
1 
1      $ git diff            Review the patch one more time
1      $ git add ...         Add any files for committing
1      $ git commit          Commit the files. Include a commit message.
1      $ git push            Push the files up to the repo. Ta da!
1 
11    The first three steps are the same described earlier (⇒Starting
 A New Branch).  The 'git push' is what's new, and it updates the repo
1 on Savannah.  Congratulations!
1 
1    As a courtesy, you should send a note to the mailing list indicating
1 that you have pushed your change.
1