Changes between Version 7 and Version 8 of CodingGuidelines/SubmittingPatches


Ignore:
Timestamp:
Aug 6, 2012 6:24:20 PM (7 years ago)
Author:
axeld
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodingGuidelines/SubmittingPatches

    v7 v8  
    1414=== Preparing to create patch file ===
    1515 * Create patches from within the ''HAIKU_TOP'' directory. This is the directory that contains ''configure'' and typically is the ''haiku/'' or ''buildtools/'' branch.
    16         * {{{ git status }}} will display which files are modified, added, or deleted
    17         * Perform a git diff...
    18                 * {{{ git diff > ~/DescriptiveName.patch }}}
    19                 * {{{ git diff or/specify/per/file or/specify/directory/ > ~/DescriptiveName.patch }}}
    20         * ''Note:'' If patching newly created files, {{{ git add <path-to-new-file> }}} needs to be done before {{{ git diff }}}
     16        * {{{ git status }}} will display which files are modified, added, or deleted. Use `git diff` to inspect your changes.
     17        * 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.
     18        * Now, you need to create the actual patch file that you can, for example, attach to a ticket:
     19                * `git format-patch <commitsha or branch name>` - this will create a file named 0001-your-commit-message.patch.
    2120
    2221=== Submitting the patch ===