On Mon, Jan 20, 2020 at 12:29 AM Andreas Fritiofson < [email protected]> wrote:
> > > On Fri, Jan 17, 2020 at 4:24 PM Antonio Borneo <[email protected]> > wrote: > >> On Fri, Jan 17, 2020 at 3:37 PM Oleksij Rempel <[email protected]> >> wrote: >> > >> > Am 17.01.20 um 12:45 schrieb Antonio Borneo: >> is there any method to force jenkins to rebuild a patch before merging >> it? Maybe has to be rebased on top of master. >> >> > I don't think there's an option to do that. But we can get a similar > effect by switching submit strategy from Cherry-Pick to Fast-forward Only. > That way the submitter must manually rebase changes in the same order as > they will end up in master. So in effect, the submit will only fast-forward > master to a commit that has previously been built. > That will require every patch to be rebased before submitting, which means that a maintainer can't select more than one patch at a time to merge. Given that maintainers already seem to have very little time to review/merge patches, I prefer the status quo. Breakage has been rare, and at least it makes it possible for sometimes a bunch of patches are all merged together. Tim
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
