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-23 17:58] mricon |
userdoc:patchwork [2018-11-28 02:25] 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) | ||
+ | - Auto-supersede series? (yes, within NN days/no) | ||
+ | - Auto-archive old patches? (yes, when older than NN days/no) | ||
+ | ==== Auto-superseding series and archiving old patches ==== | ||
+ | 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 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 | ||
+ | |||
+ | Similarly, the bot can archive patches older than a certain period of time. | ||
+ | |||
+ | ==== 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: | ||
+ | |||
+ | <file> | ||
+ | Subject: Your patches were applied to shuah/linux-kselftest.git | ||
+ | From: patchwork-bot@kernel.org | ||
+ | To: Submitter Name <submitter@kernel.org> | ||
+ | |||
+ | Hello: | ||
+ | |||
+ | The following patches you sent were recently pushed to | ||
+ | shuah/linux-kselftest.git (refs/heads/next): | ||
+ | |||
+ | media: rc: self test for IR encoders and decoders | ||
+ | Status : Accepted | ||
+ | Patchwork: https://patchwork.kernel.org/patch/10643585 | ||
+ | Webview : https://git.kernel.org/shuah/linux-kselftest/c/e55c884ea5c66a29a713d41ed0819fee8038762b | ||
+ | |||
+ | media: [something else] | ||
+ | Status : Accepted | ||
+ | Patchwork: https://patchwork.kernel.org/patch/x | ||
+ | Webview : https://git.kernel.org/shuah/linux-kselftest/c/x | ||
+ | |||
+ | media: [and another one] | ||
+ | Status : Accepted | ||
+ | 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! | ||
+ | |||
+ | -- | ||
+ | Deet-doot-dot, I am a bot. | ||
+ | https://korg.wiki.kernel.org/userdoc/pwbot | ||
+ | </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). |