On Tue, Apr 12, 2016 at 07:52:02AM -0700, Stefan Beller wrote: > On Tue, Apr 12, 2016 at 12:23 AM, Matthieu Moy > <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > > Stefan Beller <sbeller@xxxxxxxxxx> writes: > > > >> Hi Greg, > >> > >> Thanks for your talk at the Git Merge 2016! > >> The Git community uses the same workflow as the kernel. So we may be > >> interested in the 0 bot which could compile and test each patch on the list. > > > > In the case of Git, we already have Travis-CI that can do rather > > thorough testing automatically (run the complete testsuite on a clean > > machine for several configurations). You get the benefit from it only if > > you use GitHub pull-requests today. > > But who uses that? (Not a lot of old-timers here, that's for sure) > > > It would be interesting to have a > > bot watch the list, apply patches and push to a travis-enabled fork of > > git.git on GitHub to get the same benefit when posting emails directly > > to the list. > > That is better (and probably more work) than what I had in mind. > IIUC the 0 bot can grab a patch from a mailing list and apply it to a > base (either the real base as encoded in the patch or a best guess) > and then run "make". > > At least that's how I understand the kernel setup. So my naive thought > is that the 0 bot maintainer "only" needs to add another mailing list > to the watch list of the 0 bot? yes, this is feasible in 0 bot, though it requires some refactoring to current mailing list logic which focuses on linux kernel like using guess work to find out which maintainer tree to apply a patch on by following a set of rules. After the current proposal to add extra info to git-format-patch is accepted, this can be more smooth. > > Stefan > > > > > -- > > 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