I've used my free time in the last week to look over the 5246 patches which were sent to the B.A.T.M.A.N. mailing list. These patches were categorized as
* Accepted: committed to the respective repository at git.open-mesh.org * Rejected: Either rejected by the Maintainer(s) or withdrawn by the Author because they turned out to be a bad idea * RFC patches which were just posted to get comments * Not applicable patches which were not really for a repository at git.open-mesh.org (for example patches which are forwarded to net-next.git/net.git) * Changes requested Patch had flaws but these could be fixed but the author of the patch hasn't sent a new version of the patch * Superseded New version of the patch(set) was sent which makes the old version obsolete
The result can now be found at https://patchwork.open-mesh.org/
You may wonder why are there patches with the state "New" + "Delegate" set to some person. These are the patches which have not yet been applied in their respective repository at git.open-mesh.org, not yet rejected and not yet replaced by a different patch. Ok, these are most likely not all still waiting to be applied but I just didn't know their state and thus the maintainer(s) have to look over the remaining patches and change their state. Until then, these are added to the TODO list of the maintainer .
Patchwork is currently configured to read the mails which are sent to firstname.lastname@example.org and add each patch + its comments to the patchwork database. Maintainers can then update their state, download the patches and bundle them (which then can be downloaded again). A heuristic was installed in the post-receive hook that tries to find the correct commit for a newly applied patch in the master branch and automatically mark them as Accepted.
The author of an patch will be automatically informed about changes to the state of his patch.
I have already started to assign the patches with the state "New" to the maintainers. This is also the reason why Marek, Simon and Elektra will not be able to create their own account and instead will receive a mail from me with their account data.
But also other people can help here. They can register to set the state of their own patches. This is for example helpful when they've just submitted a new patchset and want to mark the old patchset as superseded. But they can of course also disable the notification mails.
I hope this helps to better keep track on the incoming patches and make it harder to forget one.
Kind regards, Sven