@@ -89,29 +89,29 @@ latest source with Git: Now that you have a copy of the project, create a new local branch: - $ git checkout -b my_bug_fix + $ git checkout -b my-bug-fix -This new branch, my_bug_fix, is where all of your changes should go. +This new branch, my-bug-fix, is where all of your changes should go. There is always the possibility that new changes will be pushed to the remote -repository while you make your changes in the my_bug_fix branch. The best way to +repository while you make your changes in the my-bug-fix branch. The best way to keep up-to-date with these changes is to pull them from the remote repository -and use them as the new base for the my_bug_fix branch: +and use them as the new base for the my-bug-fix branch: $ git checkout master $ git pull - $ git rebase master my_bug_fix + $ git rebase master my-bug-fix The changes from the remote repository are pulled into your local master branch, providing you with the most recent base to apply your changes. The changes from -your my_bug_fix branch will then use the most recent changes you pulled from the +your my-bug-fix branch will then use the most recent changes you pulled from the remote repository as their base. Finally, create the patch that you plan on submitting: - $ git format-patch master --stdout > my_bug_fix.diff + $ git format-patch master --stdout > my-bug-fix.diff -This patch, my_bug_fix.diff, now contains all of your changes. Please, be sure +This patch, my-bug-fix.diff, now contains all of your changes. Please, be sure to provide your patch with a detailed description of your changes. # Acknowledgments README 08028eee78a9b5e9eb703254da252c837031c837 eczarny eczarny@gmail.com http://github.com/eczarny/xmlrpc/commit/ad796b5dabc628bddcd2f370733a3a3afc9e8ae5 ad796b5dabc628bddcd2f370733a3a3afc9e8ae5 2008-12-17T16:03:08-08:00 2008-12-17T16:03:08-08:00 Minor documentation update. faef3fa869d8c7aeead37532074b1c6c25112024 eczarny eczarny@gmail.com