Changes between Version 9 and Version 10 of CodingGuidelines/SubmittingPatches
- Timestamp:
- Nov 10, 2013, 10:26:31 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CodingGuidelines/SubmittingPatches
v9 v10 18 18 * You'll then have to commit the patch locally by adding the changed or added files (`git add my-file my/new/file`), and then do a `git commit`. You will need to enter a complete commit message that will later appear as is in Haiku's repository if your patch is going to be accepted. 19 19 * Now, you need to create the actual patch file that you can, for example, attach to a ticket: 20 * `git format-patch <commitsha or branch name>` - this will create a file named 0001-your-commit-message.patch. 20 * `git format-patch <commitsha or branch name>` - this will create a file named 0001-your-commit-message.patch. (Note: Depending on your workflow, `git format-patch HEAD~1` may also suffice) 21 21 22 22 === Submitting the patch ===