Le 19/09/2017 à 17:43, Johannes Schindelin a écrit : > > C'mon, don't *try* to misunderstand me. > > Of course there need to be updates as to the state of patch series. > > It's just that mails only go *so* far when you need to connect and > aggregate information. You need the connection between the original patch > series, the latest unaddressed reviews, links to the branches, history of > the patch series' iterations, and ideally links to the repositories of the > contributors with *their* branch names. And then, of course, your verdict > as to the state of the patch series and your expectation what happens > next. > > To relate that, you are using a plain text format that is not well defined > and not structured, and certainly not machine-readable, for information > that is crucial for project management. > > What you need is a tool to aggregate this information, to help working > with it, to manage the project, and to be updated automatically. And to > publish this information continuously, without costing you extra effort. > > I understand that you started before GitHub existed, and before GitHub was > an option, the script-generated What's cooking mail was the best you could > do. > > Ciao, > Dscho Hi, Would something like patchwork fix your need ? They now seems to have a REST API, which means it could probably be pluggeg into Junio's scripts and work seemlessly for him (or any other happy ML user) while other people can browse through the web interface. I used to work with this one: http://patches.opendataplane.org/project/lng-odp/list/ It is not the best example as the patch status are pretty much never updated on this one. But it would solve most of the points you raised, while keeping fully compatible with the way people actually work (including Junio). Nicolas
