User Tools

Site Tools


userdoc:patchwork

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 Both sides next revision
userdoc:patchwork [2018-11-23 18:33]
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)
  
-If you choose to notify submitters, it would send them a summary email per all patches ​applied ​within one session, ​e.g.:+==== 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>​ <​file>​
userdoc/patchwork.txt · Last modified: 2020-05-08 14:58 by mricon