On Mon, Mar 24 2014, John Dennis wrote: > But from that point forward it appears as if each commit is handled > independently rather than being an ordered list of commits that are > grouped together sharing a single review where their relationship is > explicit. Also the jenkins tests either needs to apply all the commits > in sequence and run the test or it needs to run the test after applying > the next commit in the sequence. > > Can someone provide some explanation on how to handle this situation? > > Or perhaps I'm just not understanding how the tools work when multiple > commits are submitted.
If a patch depends on another one, Jenkins is run with all the needed patches applied. -- Julien Danjou ;; Free Software hacker ;; http://julien.danjou.info
signature.asc
Description: PGP signature
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
