Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| submitting-patches [2023/12/11 21:15] – [Deciding where to send the patch] Links to specific repo's contribution guidelines efahlgren | submitting-patches [2024/06/17 08:59] – old revision restored (2024/01/03 07:44) svanheule | ||
|---|---|---|---|
| Line 70: | Line 70: | ||
| - 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, | - Staging trees can be hosted as part of the projects git infrastructure, | ||
| + | ===== Patch backports ===== | ||
| + | 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 '' | ||
| + | <code bash> | ||
| + | $ git cherry-pick --signoff -x < | ||
| + | </ | ||
| ===== Patch checklist ===== | ===== Patch checklist ===== | ||
| - Single commit ( multiple commits must first be squashed, as described [[docs: | - Single commit ( multiple commits must first be squashed, as described [[docs: | ||