Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: >>>> True, presumably the Travis integration already solves that part, so >>>> I suspect it is just the matter of setting up: >>>> >>>> - a fork of git.git and have Travis monitor any and all new >>>> branches; >>>> >>>> - a bot that scans the list traffic, applies each series it sees to >>>> a branch dedicated for that series and pushes to the above fork. >>> >>> ... and to make it really useful: a way to get a notification email sent >>> on-list or at least to the submitter as a reply to the patch series. >> Travis CI could do this ... > The missing part would be "as a reply to the patch series". When I start > reviewing a series, if the patch is broken and the CI system already > knows, I'd rather have the information attached in the same thread right > inside my mailer. Yeah, such a message thrown randomly at the list would be too noisy to be useful, but if it is sent to a specific thread as a response, it would grab attention of those who are interested in the series, which is exactly what we want. So with what you added, the list of what is needed is now: - a fork of git.git and have Travis monitor any and all new branches; - a bot that scans the list traffic, applies each series it sees to a branch dedicated for that series and pushes to the above fork; - a bot (which can be the same as the above or a different one, as long as the former and the latter has a way to associate a topic branch and the original message) that receives success/failure notice from Travis, relays it as a response to the original patch on the list. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html