userdoc:patchwork
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
userdoc:patchwork [2018-11-28 02:25] mricon |
userdoc:patchwork [2018-12-12 15:26] mricon |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| - Summary to: (e.g. example@kernel.org, example@gmail.com) | - Summary to: (e.g. example@kernel.org, example@gmail.com) | ||
| - Notify submitters?: (yes/no) | - Notify submitters?: (yes/no) | ||
| + | - (If yes on previous) Get cc'd on notifications? (yes/no) | ||
| - Auto-supersede series? (yes, within NN days/no) | - Auto-supersede series? (yes, within NN days/no) | ||
| - Auto-archive old patches? (yes, when older than NN days/no) | - Auto-archive old patches? (yes, when older than NN days/no) | ||
| Line 25: | Line 26: | ||
| The bot can do some basic housekeeping chores, such as automatically marking patches belonging to older versions of the series as "superseded." E.g. if a contributor sends "''[PATCH NN/30] Do foo to bar''", and then after that a new revision "''[PATCH NN/30 v2] Do foo to bar''", the bot can automatically mark the 30 patches belonging to the "''v1''" of the series as "superseded". In order to work, the following conditions must be met: | The bot can do some basic housekeeping chores, such as automatically marking patches belonging to older versions of the series as "superseded." E.g. if a contributor sends "''[PATCH NN/30] Do foo to bar''", and then after that a new revision "''[PATCH NN/30 v2] Do foo to bar''", the bot can automatically mark the 30 patches belonging to the "''v1''" of the series as "superseded". In order to work, the following conditions must be met: | ||
| - | - It must be submitted by the same person | + | - It must be submitted by the same person |
| - | - It must have the exact same series name (first patch or cover letter subject wording) | + | - It must have the exact same series name (first patch or cover letter subject wording) |
| - | - It must be within the cutoff period of days specified. In other word, if the cutoff is 90 days and the new series comes in 4 months later, there will be no match | + | - It must be within the cutoff period of days specified. In other word, if the cutoff is 90 days and the new series comes in 4 months later, there will be no match |
| - | Similarly, the bot can archive patches older than a certain period of time. | + | Similarly, the bot can archive patches older than a certain period of time if they are still in the "New" state. |
| ==== Notifying submitters ==== | ==== Notifying submitters ==== | ||
| - | If you choose to notify submitters, it would send them a summary email per all patches marked as "Accepted" within one session, for example: | + | If you choose to notify submitters, it would send them a summary email per each series that was marked as accepted, for example: |
| <file> | <file> | ||
| - | Subject: Your patches were applied to shuah/linux-kselftest.git | + | Subject: Re: [PATCH v3,00/03] Apply foo to bar |
| - | From: patchwork-bot@kernel.org | + | From: patchwork-bot+project-name@kernel.org |
| To: Submitter Name <submitter@kernel.org> | To: Submitter Name <submitter@kernel.org> | ||
| Hello: | Hello: | ||
| - | The following patches you sent were recently pushed to | + | This series was applied to shuah/linux-kselftest (refs/heads/fixes). |
| - | shuah/linux-kselftest.git (refs/heads/next): | + | |
| - | media: rc: self test for IR encoders and decoders | + | On Fri, 07 Dec 2018 11:09:48 +0100 you wrote: |
| - | Status : Accepted | + | > The foo is not applied to bar, but it should be. |
| - | Patchwork: https://patchwork.kernel.org/patch/10643585 | + | > |
| - | Webview : https://git.kernel.org/shuah/linux-kselftest/c/e55c884ea5c66a29a713d41ed0819fee8038762b | + | > Signed-off-by: Awesome Contributor <awesome@example.com> |
| - | media: [something else] | + | Here is a summary with links: |
| - | Status : Accepted | + | - [1/3] Apply foo to bar |
| - | Patchwork: https://patchwork.kernel.org/patch/x | + | https://git.kernel.org/[...] |
| - | Webview : https://git.kernel.org/shuah/linux-kselftest/c/x | + | - [2/3] Apply foo to bar with more conviction |
| - | + | https://git.kernel.org/[...] | |
| - | media: [and another one] | + | - [3/3] Apply foo to bar for real this time |
| - | Status : Accepted | + | https://git.kernel.org/[...] |
| - | Patchwork: https://patchwork.kernel.org/patch/x | + | |
| - | Webview : https://git.kernel.org/shuah/linux-kselftest/c/x | + | |
| - | + | ||
| - | Total patches: 3 | + | |
| You are awesome, thank you! | You are awesome, thank you! | ||
| Line 69: | Line 65: | ||
| </file> | </file> | ||
| - | This way, if you are applying a series of 50 patches from the same person, the submitter will only receive a single notification email (as long as you push them in one batch). | + | This way, if you are applying a series of 50 patches from the same person, the submitter will only receive a single notification email. |
userdoc/patchwork.txt · Last modified: 2020-05-08 14:58 by mricon
Page Tools
