Patchwork is a tool to help track patches sent to a mailing list, to make sure they are not lost in the traffic or otherwise overlooked.
To get a new project added to patchwork, please send an email request to support with the following info:
If you have your git tree on git.kernel.org, you can send a request to support to request patchwork-bot integration. Please provide all of the following info as part of your request:
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:
Similarly, the bot can archive patches older than a certain period of time if they are still in the "New" state.
If you choose to notify submitters, it would send them a summary email per each series that was marked as accepted, for example:
Subject: Re: [PATCH v3,00/03] Apply foo to bar From: firstname.lastname@example.org To: Submitter Name <email@example.com> Hello: This series was applied to shuah/linux-kselftest (refs/heads/fixes). On Fri, 07 Dec 2018 11:09:48 +0100 you wrote: > The foo is not applied to bar, but it should be. > > Signed-off-by: Awesome Contributor <firstname.lastname@example.org> Here is a summary with links: - [1/3] Apply foo to bar https://git.kernel.org/[...] - [2/3] Apply foo to bar with more conviction https://git.kernel.org/[...] - [3/3] Apply foo to bar for real this time https://git.kernel.org/[...] You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.wiki.kernel.org/userdoc/pwbot
This way, if you are applying a series of 50 patches from the same person, the submitter will only receive a single notification email.