Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
submitting-patches [2019/03/23 15:37] – merged with another article about patches bobafetthotmailsubmitting-patches [2024/06/17 08:59] – old revision restored (2024/01/03 07:44) svanheule
Line 1: Line 1:
 ====== Submitting patches ====== ====== Submitting patches ======
 +See also:
 +  * [[docs:guide-developer:working-with-git-email|Sending patches by git send-email]]
 +  * If you are using GitHub, read also [[docs:guide-developer:working-with-github-pr|Working with GitHub]].
  
-See also [[docs:guide-developer:faq-development|Development FAQ]] +=====Deciding where to send the patch===== 
  
-If you are using Github read also [[docs:guide-developer:working-with-github-pr|Working with Github]].+  * **Patches to core packages and patches that add support for new devices** (i.e. code that is in [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=summary|the main OpenWrt repository]] ) can be submitted as a pull request on [[https://github.com/openwrt/openwrt|the GitHub mirror]] or via the mailing list.
  
-Patches can be submitted as a pull request on Github or via the mailing list.+  * **Patches for LuCI web interface and related packages** can be submitted to mailing list or to the [[https://github.com/openwrt/luci/| Github mirror]] of the LuCI git repository.  Specific guidelines and hints for contributing to the //LuCI// repo may be found at [[https://github.com/openwrt/luci/blob/master/CONTRIBUTING.md| Contributing Guidelines]].
  
-Submissions should follow the following guidelines:+  * **Patches for community packages about routing** should go as a Github PR in the [[https://github.com/openwrt-routing/packages| OpenWrt community routing packages repo]].  Use the //packages// contributing guidelines below when contributing to the //routing// repo.
  
-  * use a different git branch for each pull request (GitHub does this automatically if you edit files through the website)+  * **Patches for community packages about telephony and SIP/VOIP** should go as a Github PR in the  [[https://github.com/openwrt/telephony| OpenWrt community telephony packages repo]].  Use the //packages// contributing guidelines below when contributing to the //telephony// repo.
  
-  * write commit subject and message in the imperative form"add support for X", NOT "added support for X"+  * **Patches for miscellaneous community packages** should go as a Github PR in the [[https://github.com/openwrt/packages|OpenWrt community package repo]].  Specific guidelines and hints for contributing to the //packages// repo may be found at [[https://github.com/openwrt/packages/blob/master/CONTRIBUTING.md| Contributing Guidelines]].
  
 +<WRAP round info 60%>
 +**If you want to add a new package that is not specific for a device** nor crucial to compile or use OpenWrt on a device, (i.e. tools, compilers, runtimes libraries, VPNs, media servers, backup servers and more), **open a PR in the appropriate community packages repository mentioned above.** Note that if you add a package you usually must assign yourself as "maintainer" of it.
 +</WRAP>
 + 
 +
 +===== Submission Guidelines =====
 +
 +Submissions should follow the following guidelines:
 +  * use a different git branch for each pull request (GitHub does this automatically when using web interface)
 +  * write commit subject and message in the imperative form: "add support for X", NOT "added support for X"
   * **code formatting**   * **code formatting**
     * use the same indentation you find in the file you are modifying, use only tabs or only spaces depending on what was done in the rest of the file     * use the same indentation you find in the file you are modifying, use only tabs or only spaces depending on what was done in the rest of the file
Line 34: Line 47:
     * If you add support for new hardware: Include in your commit message a short description of the hardware and how to install OpenWrt on it. Have a look at the [[https://git.openwrt.org/?p=openwrt/openwrt.git&a=search&h=HEAD&st=commit&s=add+support+for|recent additions]] for some examples.     * If you add support for new hardware: Include in your commit message a short description of the hardware and how to install OpenWrt on it. Have a look at the [[https://git.openwrt.org/?p=openwrt/openwrt.git&a=search&h=HEAD&st=commit&s=add+support+for|recent additions]] for some examples.
  
-  * **all commits must contain ''%%Signed-off-by: My Name <my@email.address>%%'' where you write your real name and real email address**, in accordance with [[http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=HEAD#n416|Section 11 of the Linux Kernel patches guide]]. +  * **all commits must contain ''%%Signed-off-by: My Name <my@email.address>%%'' where you write your real name and real email address**, in accordance with [[http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=HEAD#n416|Section 11 of the Linux Kernel patches guide]] 
-    * it can be done automatically by git commandline with<code>git commit --signoff</code>+    * GitHub web interface or GUI application for git: you must append the ''Signed-off-by:'' line manually in the commit description 
 +    * git command-line interface:
  
-  * the Author field **must** match the "Signed-off-by:" line  +<code bash
-    * if you are editing files and committing through GitHub, you must write your real name in the "Name" field in GitHub settings and the email used in the "Signed-off-by:" must be your primary github email +git commit --signoff 
-    * if you are editing files and committing on your local PC, set your name and email with<code> +</code>
-git config --global user.name "my name" +
-git config --global user.email "my@email.address"</code>+
  
-===== Patch Merging And Tree Life Cycle =====+  * **the ''Author'' field must match the ''Signed-off-by:'' line** 
 +    * GitHub web interface: you must specify your real name in the ''Name'' field and the ''Primary email address'' to match the ''Signed-off-by:'' line 
 +    * git command-line interface:
  
-We encourage frequent committers to host their own staging trees where they aggregate patches that they feel responsible for and/or ones that they created themselvesOnce the tree has been reviewed and tested it can be proposed for inclusion in the master branch.+<code bash> 
 +git config --global user.name "my name" 
 +git config --global user.email "my@email.address" 
 +</code>
  
 +===== Patch merging and tree life cycle =====
 +We encourage frequent committers to host their own staging trees where they aggregate patches that they feel responsible for and/or ones that they created themselves. Once the tree has been reviewed and tested it can be proposed for inclusion in the master branch.
   - Trees will be merged into master at any time   - Trees will be merged into master at any time
   - Bug fixes can be merged into master directly   - Bug fixes can be merged into master directly
   - PRs can be sent to the patches mailing list from any source and will always be considered for inclusion if the quality of the tree is good and format of submission is correct   - PRs can be sent to the patches mailing list from any source and will always be considered for inclusion if the quality of the tree is good and format of submission is correct
   - Staging trees can be hosted as part of the projects git infrastructure, private servers, GitHub ...   - Staging trees can be hosted as part of the projects git infrastructure, private servers, GitHub ...
- +===== Patch backports ===== 
-===== Patch Checklist =====+Backporting refers to applying changes to a stable (release) branch like for example **openwrt-23.05** from the **main** branch. Since new features are not added to stable branches, backported changes are generally bug fixes and security fixes only. The process is roughly following: 
 +  - Changes needs to be first applied into the **main** branch 
 +  - Afterwards those changes can be proposed to be applied into the stable (release) branch 
 +When pulling the commits from the **main** branch, you need to use ''git cherry-pick'' command with the ''-x'' argument and thus append a line that says ''(cherry picked from commit <commit>)'' to the original commit message ([[https://github.com/openwrt/openwrt/commit/59fd8f08cf544a7f0fcaf700ca9af9292de3adcc.patch|example]]) in order to indicate which commit this change was cherry-picked from. This is needed for traceability. It is also required that you add the ''--signoff'' to the commits, if you did not create the original commits. 
 +<code bash> 
 +$ git cherry-pick --signoff -x <commit> 
 +</code> 
 +===== Patch checklist =====
   - Single commit ( multiple commits must first be squashed, as described [[docs:guide-developer:working-with-github-pr#squashing_commits|here]]  )   - Single commit ( multiple commits must first be squashed, as described [[docs:guide-developer:working-with-github-pr#squashing_commits|here]]  )
   - Subject < 50 characters   - Subject < 50 characters
Line 65: Line 91:
   - Sender/Author name and email address matches Signoff line's real name and email address    - Sender/Author name and email address matches Signoff line's real name and email address 
  
-===== DTS Checklist =====+===== DTS checklist =====
   - Don't forget to add proper license, consider adding ''SPDX-License-Identifier: GPL-2.0-or-later OR MIT'' ([[https://github.com/openwrt/openwrt/commit/221d3e023451cad0b60b8a47e8b788d6368108c2#diff-7ecb7639c5199e391573618b0e444894|details]])   - Don't forget to add proper license, consider adding ''SPDX-License-Identifier: GPL-2.0-or-later OR MIT'' ([[https://github.com/openwrt/openwrt/commit/221d3e023451cad0b60b8a47e8b788d6368108c2#diff-7ecb7639c5199e391573618b0e444894|details]])
   - Remove all ocurrencies of ''default-state = "off"'' properties under your LED nodes ([[https://github.com/openwrt/openwrt/commit/0d23fd2ab29a66f5d03187db4fac3e396b4f3b62|details]])   - Remove all ocurrencies of ''default-state = "off"'' properties under your LED nodes ([[https://github.com/openwrt/openwrt/commit/0d23fd2ab29a66f5d03187db4fac3e396b4f3b62|details]])
   - If you're adding MTD flash layout, and you've ''label = "firmware"'' or a node with the name ''firmware@xyz'', please check that you've added proper ''compatible'' property (if applicable) ([[https://github.com/openwrt/openwrt/pull/1586/commits/22c1d69e63a3e80c41baf3941d5e6deb2019d039|details]])   - If you're adding MTD flash layout, and you've ''label = "firmware"'' or a node with the name ''firmware@xyz'', please check that you've added proper ''compatible'' property (if applicable) ([[https://github.com/openwrt/openwrt/pull/1586/commits/22c1d69e63a3e80c41baf3941d5e6deb2019d039|details]])
-  - If it's possible try to dedicate some of the LEDs for system status indication in [[https://github.com/openwrt/openwrt/blob/master/package/base-files/files/etc/diag.sh|diag.sh]] ([[https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca9533_tplink_tl-wr841-v11.dts#L13|example]])+  - If it's possible try to dedicate some of the LEDs for system status indication in [[https://github.com/openwrt/openwrt/blob/master/package/base-files/files/etc/diag.sh|diag.sh]] ([[https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca9533_tplink_tl-wr841-v11.dtsi#L7|example]])
   - The name of a node should reflect the function of the device and not its model. Examples for generic node names can be found in Section [[https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation|2.2.2 Generic Names Recommendation]]   - The name of a node should reflect the function of the device and not its model. Examples for generic node names can be found in Section [[https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation|2.2.2 Generic Names Recommendation]]
   - Remove all [[https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#device_type-deprecated|deprecated "device_type"]] properties, unless for "memory" or "cpu" nodes   - Remove all [[https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#device_type-deprecated|deprecated "device_type"]] properties, unless for "memory" or "cpu" nodes
  
 +An overview of non-mandatory guidelines for device support submissions is provided in [[docs:guide-developer:device-support-policies|Device support policies / best practices]]
 ===== In-depth process of preparing and submitting code to OpenWrt ===== ===== In-depth process of preparing and submitting code to OpenWrt =====
 Based on [[https://www.kernel.org/doc/html/latest/process/submitting-patches.html|​Linux Kernel patch submission guidelines]]. Based on [[https://www.kernel.org/doc/html/latest/process/submitting-patches.html|​Linux Kernel patch submission guidelines]].
  
-OpenWrt is constantly being improved. We'd like as many people to contribute to this as we can get. If you find a change useful, by all means try to get it incorporated into the project. This should improve OpenWrt and it should help carry your changes forward into future versions+OpenWrt is constantly being improved. We'd like as many people to contribute to this as we can get. If you find a change useful, by all means try to get it incorporated into the project. This should improve OpenWrt and it should help carry your changes forward into future versions.
  
 For a person or company who wishes to submit a change to OpenWrt, the process can sometimes be daunting if you're not familiar with "the system." This text is a collection of suggestions which can greatly increase the chances of your change being accepted. For a person or company who wishes to submit a change to OpenWrt, the process can sometimes be daunting if you're not familiar with "the system." This text is a collection of suggestions which can greatly increase the chances of your change being accepted.
- 
-This document tries to lay out a procedure to enable people to submit patches in a way that is most effective for all concerned. 
  
 It is important to do all these steps repeatedly: It is important to do all these steps repeatedly:
 +  * Listen to what other people think.
 +  * Explain what problem you are addressing and your proposed solution.
 +  * Write useful patches including documentation.
 +  * Test, test, test.
  
-    listen to what other people think +Where to listen and talk:
-    talk explaining what problem you are addressing and your proposed solution +
-    do write useful patches including documentation +
-    test test test +
- +
-where to listen and talk +
   * Google to find things related to your problem   * Google to find things related to your problem
-  * Wiki: check this [[:start|OpenWrt wiki]] +  * [[:start|OpenWrt wiki]] 
-  * ​Mailing Lists +  * ​[[:contact#mailing_lists|Mailing Lists]] 
-  * Forums like [[https://forum.openwrt.org]] +  * [[:contact#irc_channels|IRC]] 
-  * IRC irc.freenode.net, channels #openwrt and #openwrt-devel +  * [[https://forum.openwrt.org|OpenWrt Forum]] 
-  * TRAC ​​https://dev.openwrt.org/ the issue/bug/change tracking system. (TRAC is closed now, and only kept for archiving purposes.) +  * GitHub - ​https://github.com/openwrt/openwrt - trunk development and bugtracking 
-  * Github - ​http://github.com/openwrt - trunk development, and bugtracking has been moved here.+  * (archived) TRAC ​​https://dev.openwrt.org/ the issue/bug/change tracking system. (TRAC is closed now, and only kept for archiving purposes.)
  
 ===== Documentation ===== ===== Documentation =====
 It is often best to document what you are doing before you do it. The process of documentation often exposes possible improvements. Keep your documentation up to date. It is often best to document what you are doing before you do it. The process of documentation often exposes possible improvements. Keep your documentation up to date.
  
-===== Creating and Sending your change =====+===== Creating and sending your change =====
 Read [[:submitting-patches#patch_checklist|Submit Checklist]] for a list of items to check before submitting code. Read [[:submitting-patches#patch_checklist|Submit Checklist]] for a list of items to check before submitting code.
  
-For patches against external package sources, refer to the quilt howto at [[docs:guide-developer:patches]]+For patches against external package sources, refer to the quilt howto at [[docs:guide-developer:toolchain:use-patches-with-buildsystem]]
  
-Please read ​[[https://www.kernel.org/doc/html/v4.11/process/email-clients.html|Email Clients for Patches]] to find out how to make sure your email client doesn't destroy your patch.+Please read ​[[https://www.kernel.org/doc/html/v4.11/process/email-clients.html|Email clients for patches]] to find out how to make sure your email client doesn't destroy your patch.
  
 ==== 1. Creating a patch ===== ==== 1. Creating a patch =====
- 
 All changes to OpenWrt occur in the form of patches. All changes to OpenWrt occur in the form of patches.
  
 Patches should be based in the root trunk, not in any lower subdirectory. Patches should be based in the root trunk, not in any lower subdirectory.
  
-Make sure your patch does not include any extra files which do not belong in a patch submission. Make sure to review your patch -afteryou have generated it, to ensure accuracy.+Make sure your patch does not include any extra files which do not belong in a patch submission. 
 +Be sure to review your patch **after** you have generated it, to ensure accuracy.
  
-If your changes produce a lot of deltas, you may want to look into splitting them into individual patches which modify things in logical stages. This will facilitate easier reviewing by other OpenWrt developers, which is very important if you want your patch to be accepted.+If your changes produce a lot of deltas, you may want to look into splitting them into individual patches which modify things in logical stages. 
 +This will facilitate easier reviewing by other OpenWrt developers, which is very important if you want your patch to be accepted.
  
 The tools you can use to create a patch, in order of preference, are: The tools you can use to create a patch, in order of preference, are:
- 
    * Git    * Git
    * SVN    * SVN
    * diff    * diff
  
-To ease integration of smaller patches into trunk, developers can also make pull-requests into the Github trunk tree - this is an addition over the earlier patchwork workflow. Larger patches, or patches that require further discussion, should still be sent to the openwrt-devel list, where they'll be commented upon, and committed into trunk at some point.+To ease integration of smaller patches into trunk, developers can also make pull-requests into the GitHub trunk tree - this is an addition over the earlier patchwork workflow. 
 +Larger patches, or patches that require further discussion, should still be sent to the **openwrt-devel** list, where they'll be commented upon, and committed into trunk at some point.
  
 ==== 2. Describe your changes ===== ==== 2. Describe your changes =====
- 
 Describe the technical detail of the change(s) your patch includes. Describe the technical detail of the change(s) your patch includes.
  
Line 142: Line 164:
 If the patch fixes a logged bug trac entry, refer to that bug entry by number. If the patch fixes a logged bug trac entry, refer to that bug entry by number.
  
-==== 3. Separate your changes===== +==== 3. Separate your changes =====
 Separate __logical changes__ into a single patch file. Separate __logical changes__ into a single patch file.
  
Line 155: Line 176:
  
 ==== 4. Style check your changes ===== ==== 4. Style check your changes =====
- 
 Check your patch for basic style violations. Failure to do so simply wastes the reviewer's time and will get your patch rejected, probably without even being read. Check your patch for basic style violations. Failure to do so simply wastes the reviewer's time and will get your patch rejected, probably without even being read.
  
 +==== 5. Select email destination =====
 +Look in the Makefile if a MAINTAINER macro exists. If so, email that person. Unless you have a reason NOT to do so, always CC openwrt-devel <at> lists.openwrt.org. If no maintainer is listed, send your patch to the [[https://lists.openwrt.org/mailman/listinfo/openwrt-devel|​primary OpenWrt developer's mailing list]]. Most OpenWrt developers monitor this email list, and can comment on your changes.
  
-==== 5. Select e-mail destination. =====+==== 6No MIME, no links, no compression, no attachments, just plain text ===== 
 +OpenWrt developers need to be able to read and comment on the changes you are submitting. It is important for an OpenWrt developer to be able to "quote" your changes, using standard email tools, so that they may comment on specific portions of your code.
  
-Look in the Makefile if a MAINTAINER macro exists. If so, e-mail that person. Unless you have a reason NOT to do soalways CC openwrt-devel <at> lists.openwrt.org. If no maintainer is listed, send your patch to the [[https://lists.openwrt.org/mailman/listinfo/openwrt-devel|​primary OpenWrt developer's mailing list]]. Most OpenWrt developers monitor this e-mail list, and can comment on your changes.+For this reason, all patches should be submitting email "inline"WARNING: Be wary of your editor's word-wrap corrupting your patch, if you choose to cut-n-paste your patch.
  
-==== 6. No MIME, no links, no compression, no attachments. Just plain text ===== +Do not attach the patch as a MIME attachment, compressed or not. Many popular email applications will not always transmit a MIME attachment as plain text, making it impossible to comment on your code.
- +
-OpenWrt developers need to be able to read and comment on the changes you are submitting. It is important for an OpenWrt developer to be able to "quote" your changes, using standard e-mail tools, so that they may comment on specific portions of your code. +
- +
-For this reason, all patches should be submitting e-mail "inline". WARNING: Be wary of your editor's word-wrap corrupting your patch, if you choose to cut-n-paste your patch. +
- +
-Do not attach the patch as a MIME attachment, compressed or not. Many popular e-mail applications will not always transmit a MIME attachment as plain text, making it impossible to comment on your code.+
  
 Exception: If your mailer is mangling patches then someone may ask you to re-send them using MIME. Exception: If your mailer is mangling patches then someone may ask you to re-send them using MIME.
  
 Mozilla Thunderbird requires that you change email defaults to send plain text email. Mozilla Thunderbird requires that you change email defaults to send plain text email.
-read [[http://kb.mozillazine.org/Plain_text_e-mail_%28Thunderbird%29|Plain text e-mail - Thunderbird]]+read [[http://kb.mozillazine.org/Plain_text_e-mail_%28Thunderbird%29|Plain text email - Thunderbird]]
 :!: disable flowed text :!: disable flowed text
  
-==== 7. E-mail size ===== +==== 7. Email size =====
 Large changes are not appropriate for mailing lists, and some maintainers. If your patch, uncompressed, exceeds 300 kB in size, it is preferred that you store your patch on an Internet-accessible server, and provide instead a URL (link) pointing to your patch. Large changes are not appropriate for mailing lists, and some maintainers. If your patch, uncompressed, exceeds 300 kB in size, it is preferred that you store your patch on an Internet-accessible server, and provide instead a URL (link) pointing to your patch.
  
 +==== 8. Remain objective, re-submit =====
  
-==== 8. Don't get discouragedRe-submit =====+It's nothing personal. Code should work well for its intended purpose and results should adhere to many standards and requirements, so finding problems early is a good thing
  
 After you have submitted your change, be patient and wait. If developers like your change and apply it, it will appear as new revision in the source code management system. After you have submitted your change, be patient and wait. If developers like your change and apply it, it will appear as new revision in the source code management system.
Line 189: Line 206:
  
 Sometimes, developers may "drop" your patch with or without comment. That's the nature of the system. If your patch is dropped, it could be due to: Sometimes, developers may "drop" your patch with or without comment. That's the nature of the system. If your patch is dropped, it could be due to:
- 
    * Your patch did not apply cleanly to the latest OpenWrt revision.    * Your patch did not apply cleanly to the latest OpenWrt revision.
    * Your patch was not sufficiently discussed on openwrt-devel.    * Your patch was not sufficiently discussed on openwrt-devel.
    * A style issue.    * A style issue.
-   * An e-mail formatting issue (re-read this section).+   * An email formatting issue (re-read this section).
    * A technical problem with your change.    * A technical problem with your change.
-   * They get tons of e-mail, and yours got lost in the shuffle.+   * They get tons of email, and yours got lost in the shuffle.
    * You are being annoying.    * You are being annoying.
  
Line 201: Line 217:
  
 ==== 9. Include PATCH in the subject ===== ==== 9. Include PATCH in the subject =====
- +Due to high email traffic to openwrt-devel, it is common convention to prefix your subject line with [PATCH]. This lets OpenWrt developers more easily distinguish patches from other email discussions, and will also make its way to the patchwork automatically.
-Due to high e-mail traffic to openwrt-devel, it is common convention to prefix your subject line with [PATCH]. This lets OpenWrt developers more easily distinguish patches from other e-mail discussions, and will also make its way to the patchwork automatically.+
  
 ==== 10. Sign your work ===== ==== 10. Sign your work =====
- 
 To provide tracking of who did what, we use a "sign-off" procedure on patches that are being emailed around. To provide tracking of who did what, we use a "sign-off" procedure on patches that are being emailed around.
  
Line 240: Line 254:
 then you just add a line saying then you just add a line saying
  
-<code>+<code bash>
 Signed-off-by: Random J Developer <random@developer.example.org> Signed-off-by: Random J Developer <random@developer.example.org>
 </code> </code>
Line 246: Line 260:
 using your real name (no pseudonyms or anonymous contributions.) using your real name (no pseudonyms or anonymous contributions.)
  
-If you are a package or target maintainer, sometimes you need to slightly modify patches you receive in order to merge them, because the code is not exactly the same in your tree and the submitters'. If you stick strictly to rule (c), you should ask the submitter to rediff, but this is a totally counter-productive waste of time and energy. Rule (b) allows you to adjust the code, but then it is very impolite to change one submitter's code and make him endorse your bugs. To solve this problem, it is recommended that you add a line between the last Signed-off-by header and yours, indicating the nature of your changes. While there is nothing mandatory about this, it seems like prepending the description with your mail and/or name, all enclosed in square brackets, is noticeable enough to make it obvious that you are responsible for last-minute changes. Example :+If you are a package or target maintainer, sometimes you need to slightly modify patches you receive in order to merge them, because the code is not exactly the same in your tree and the submitters'. If you stick strictly to rule (c), you should ask the submitter to rediff, but this is a totally counter-productive waste of time and energy. Rule (b) allows you to adjust the code, but then it is very impolite to change one submitter's code and make them endorse your bugs. To solve this problem, it is recommended that you add a line between the last Signed-off-by header and yours, indicating the nature of your changes. While there is nothing mandatory about this, it seems like prepending the description with your mail and/or name, all enclosed in square brackets, is noticeable enough to make it obvious that you are responsible for last-minute changes. Example :
  
-<code>+<code bash>
 Signed-off-by: Random J Developer <random@developer.example.org> Signed-off-by: Random J Developer <random@developer.example.org>
 [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h] [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h]
Line 258: Line 272:
 Special note to back-porters: It seems to be a common and useful practise to insert an indication of the origin of a patch at the top of the commit message (just after the subject line) to facilitate tracking. For instance: Special note to back-porters: It seems to be a common and useful practise to insert an indication of the origin of a patch at the top of the commit message (just after the subject line) to facilitate tracking. For instance:
  
-<code>+<code bash>
 Date:   Wed Jul 25 15:14:50 2012 +0300 Date:   Wed Jul 25 15:14:50 2012 +0300
     [generic] add missing symbols     [generic] add missing symbols
Line 267: Line 281:
  
 For the more convenient developers, git can automatically add a sign-off: For the more convenient developers, git can automatically add a sign-off:
-<code>git commit -s</code> 
  
-==== 11. When to use Acked-by: and Cc: =====+<code bash> 
 +git commit -
 +</code>
  
-The Signed-off-by: tag indicates that the signer was involved in the development of the patch, or that he/she was in the patch's delivery path.+==== 11. When to use "Acked-by:" and "Cc:" ===== 
 +The Signed-off-by: tag indicates that the signer was involved in the development of the patch, or that they were in the patch's delivery path.
  
 If a person was not directly involved in the preparation or handling of a patch but wishes to signify and record their approval of it then they can arrange to have an Acked-by: line added to the patch's changelog. If a person was not directly involved in the preparation or handling of a patch but wishes to signify and record their approval of it then they can arrange to have an Acked-by: line added to the patch's changelog.
Line 283: Line 299:
 If a person has had the opportunity to comment on a patch, but has not provided such comments, you may optionally add a "Cc:" tag to the patch. This is the only tag which might be added without an explicit action by the person it names. This tag documents that potentially interested parties have been included in the discussion. If a person has had the opportunity to comment on a patch, but has not provided such comments, you may optionally add a "Cc:" tag to the patch. This is the only tag which might be added without an explicit action by the person it names. This tag documents that potentially interested parties have been included in the discussion.
  
-==== 12. Using Reported-by:, Tested-by: and Reviewed-by: ===== +==== 12. Using "Reported-by:""Tested-by:and "Reviewed-by:=====
 If this patch fixes a problem reported by somebody else, consider adding a Reported-by: tag to credit the reporter for their contribution. Please note that this tag should not be added without the reporter's permission, especially if the problem was not reported in a public forum. That said, if we diligently credit our bug reporters, they will, hopefully, be inspired to help us again in the future. If this patch fixes a problem reported by somebody else, consider adding a Reported-by: tag to credit the reporter for their contribution. Please note that this tag should not be added without the reporter's permission, especially if the problem was not reported in a public forum. That said, if we diligently credit our bug reporters, they will, hopefully, be inspired to help us again in the future.
  
Line 316: Line 331:
  
 A Reviewed-by tag is a statement of opinion that the patch is an appropriate modification of OpenWrt without any remaining serious technical issues. Any interested reviewer (who has done the work) can offer a Reviewed-by tag for a patch. This tag serves to give credit to reviewers and to inform maintainers of the degree of review which has been done on the patch. Reviewed-by: tags, when supplied by reviewers known to understand the subject area and to perform thorough reviews, will normally increase the likelihood of your patch getting into OpenWrt. A Reviewed-by tag is a statement of opinion that the patch is an appropriate modification of OpenWrt without any remaining serious technical issues. Any interested reviewer (who has done the work) can offer a Reviewed-by tag for a patch. This tag serves to give credit to reviewers and to inform maintainers of the degree of review which has been done on the patch. Reviewed-by: tags, when supplied by reviewers known to understand the subject area and to perform thorough reviews, will normally increase the likelihood of your patch getting into OpenWrt.
- 
  
 ==== 13. The canonical patch format ===== ==== 13. The canonical patch format =====
- 
 The canonical patch subject line is: The canonical patch subject line is:
  
-<code>+<code bash>
 Subject: [PATCH 001/123] [section] summary phrase Subject: [PATCH 001/123] [section] summary phrase
 </code> </code>
  
 The canonical patch message body contains the following: The canonical patch message body contains the following:
- 
    * A "from" line specifying the patch author.    * A "from" line specifying the patch author.
    * An empty line.    * An empty line.
    * The body of the explanation, which will be copied to the permanent changelog to describe this patch.    * The body of the explanation, which will be copied to the permanent changelog to describe this patch.
    * The "Signed-off-by:" lines, described above, which will also go in the changelog.    * The "Signed-off-by:" lines, described above, which will also go in the changelog.
-   * A marker line containing simply "---".+   * A marker line containing simply ''%%---%%''.
    * Any additional comments not suitable for the changelog.    * Any additional comments not suitable for the changelog.
    * The actual patch (diff output).    * The actual patch (diff output).
Line 339: Line 351:
  
 The "section" in the email's Subject should identify which section of OpenWrt is being patched. Some example sections are: The "section" in the email's Subject should identify which section of OpenWrt is being patched. Some example sections are:
- 
    * [a specific target name]    * [a specific target name]
    * [a specific package name]    * [a specific package name]
Line 353: Line 364:
 Some example Subjects: Some example Subjects:
  
-<code>+<code bash>
 Subject: [PATCH] e2fsprogs: Bump to 1.41.3 Subject: [PATCH] e2fsprogs: Bump to 1.41.3
-</code> +
-<code>+
 Subject: [PATCH] x86 generic: switch to 3.3 Subject: [PATCH] x86 generic: switch to 3.3
-</code> +
-<code>+
 Subject: [PATCHv2 001/207] ar71xx enable sysupgrade on the WRT160Nl Subject: [PATCHv2 001/207] ar71xx enable sysupgrade on the WRT160Nl
 </code> </code>
Line 365: Line 374:
 The "from" line must be the very first line in the message body, and has the form: The "from" line must be the very first line in the message body, and has the form:
  
-<code>+<code bash>
 From: Original Author <author@example.com> From: Original Author <author@example.com>
 </code> </code>
Line 373: Line 382:
 The explanation body will be committed to the permanent source changelog, so should make sense to a competent reader who has long since forgotten the immediate details of the discussion that might have led to this patch. Including symptoms of the failure which the patch addresses (kernel log messages, oops messages, etc.) is especially useful for people who might be searching the commit logs looking for the applicable patch. If a patch fixes a compile failure, it may not be necessary to include _all_ of the compile failures; just enough that it is likely that someone searching for the patch can find it. As in the "summary phrase", it is important to be both succinct as well as descriptive. The explanation body will be committed to the permanent source changelog, so should make sense to a competent reader who has long since forgotten the immediate details of the discussion that might have led to this patch. Including symptoms of the failure which the patch addresses (kernel log messages, oops messages, etc.) is especially useful for people who might be searching the commit logs looking for the applicable patch. If a patch fixes a compile failure, it may not be necessary to include _all_ of the compile failures; just enough that it is likely that someone searching for the patch can find it. As in the "summary phrase", it is important to be both succinct as well as descriptive.
  
-The "---marker line serves the essential purpose of marking for patch handling tools where the changelog message ends.+The ''%%---%%'' marker line serves the essential purpose of marking for patch handling tools where the changelog message ends.
  
-One good use for the additional comments after the "---marker is for a diffstat, to show what files have changed, and the number of inserted and deleted lines per file. A diffstat is especially useful on bigger patches. Other comments relevant only to the moment or the maintainer, not suitable for the permanent changelog, should also go here. A good example of such comments might be "patch changelogs" which describe what has changed between the v1 and v2 version of the patch.+One good use for the additional comments after the ''%%---%%'' marker is for a diffstat, to show what files have changed, and the number of inserted and deleted lines per file. A diffstat is especially useful on bigger patches. Other comments relevant only to the moment or the maintainer, not suitable for the permanent changelog, should also go here. A good example of such comments might be "patch changelogs" which describe what has changed between the v1 and v2 version of the patch.
  
 See more details on the proper patch format in the following References. See more details on the proper patch format in the following References.
  
-===== Monitoring Patches ===== +===== Monitoring patches ===== 
- +Patches sent to the Development mailing list can be followed on Patchwork at ​[[https://patchwork.ozlabs.org/project/openwrt/list/]].
-Patches sent to the Development mailing list can be followed on Patchwork at ​[[https://patchwork.ozlabs.org/project/openwrt/list/]]+
  
 ===== References ====== ===== References ======
- 
    * Andrew Morton, "The perfect patch" (tpp).    * Andrew Morton, "The perfect patch" (tpp).
       * ​http://userweb.kernel.org/~akpm/stuff/tpp.txt       * ​http://userweb.kernel.org/~akpm/stuff/tpp.txt
Line 403: Line 410:
       * ​http://halobates.de/on-submitting-patches.pdf       * ​http://halobates.de/on-submitting-patches.pdf
  
-===== Additional Information ===== +===== Additional information ===== 
- +  * Be aware of line length limit (80). 
-  * Be aware of line length limit (80) +  * Use ''./scripts/checkpatch.pl'' to check your patch - there might be false positives.
-  * use ''./scripts/checkpatch.pl'' to check your patch - there might be false positives+
  
  • Last modified: 2024/12/06 16:55
  • by wertwert4pda