Junio C Hamano <gitster@xxxxxxxxx> writes: > 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. Just having a web interface somewhere that knows how broken the code is would not be that useful. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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