Go to file
Jenkins 2041823504 Updated openstack/openstack
Project: openstack/heat  490fc208a0ea1423306c84a29482a2737b26eb27

Add __ne__ built-in function

In Python 3 __ne__ by default delegates to __eq__ and inverts the
result, but in Python 2 they urge you to define __ne__ when you
define __eq__ for it to work properly [1].There are no implied
relationships among the comparison operators. The truth of x==y
does not imply that x!=y is false. Accordingly, when defining
__eq__(), one should also define __ne__() so that the operators
will behave as expected.
[1]https://docs.python.org/2/reference/datamodel.html#object.__ne__

Change-Id: I3ae84db585355fef864a8beea4ad388ed09e6ff7
2016-07-19 02:23:46 +00:00
2016-07-14 10:55:47 +00:00
2016-07-07 16:41:53 +00:00
2016-07-18 13:37:17 +00:00
2016-07-15 04:31:46 +00:00
2016-06-06 15:59:11 +00:00
2016-07-18 13:07:51 +00:00
2016-06-28 10:53:00 +00:00
2016-07-18 10:23:18 +00:00
2016-07-14 14:21:33 +00:00
2016-07-18 01:54:11 +00:00
2016-06-18 12:23:01 +00:00
2016-07-14 17:38:27 +00:00
2016-07-15 04:53:34 +00:00
2016-06-03 01:39:50 +00:00
2016-07-04 08:53:36 +00:00
2016-07-15 22:20:24 +00:00
2016-07-14 16:25:17 +00:00
2016-07-18 23:53:01 +00:00
2016-07-19 00:08:49 +00:00
2016-07-14 03:19:18 +00:00
2016-07-12 21:01:10 +00:00
2016-06-27 21:50:14 +00:00
2016-07-12 11:16:36 +00:00
2016-07-13 13:46:41 +00:00
2016-07-19 02:23:46 +00:00
2016-07-11 20:46:04 +00:00
2016-07-19 00:04:51 +00:00
2016-06-08 22:14:20 +00:00
2016-07-18 18:55:03 +00:00
2016-07-14 02:22:27 +00:00
2016-07-18 23:58:17 +00:00
2016-07-15 15:58:16 +00:00
2016-07-19 01:50:27 +00:00
2016-06-07 05:34:28 +00:00
2016-07-18 14:08:24 +00:00
2016-07-19 01:05:46 +00:00
2016-07-19 01:03:21 +00:00
2016-07-19 02:17:23 +00:00
2016-07-01 14:56:49 +00:00
2016-07-09 05:18:10 +00:00
2016-07-18 10:01:43 +00:00
2016-07-13 12:25:27 +00:00
2016-07-18 22:14:29 +00:00
2016-07-11 15:26:37 +00:00
2016-07-15 01:10:06 +00:00
2016-07-13 00:38:07 +00:00
2016-07-13 17:02:19 +00:00
2016-07-18 11:12:31 +00:00
2016-07-15 00:46:47 +00:00
2016-07-13 11:22:24 +00:00
2016-06-17 14:29:13 +00:00
2016-07-13 01:56:04 +00:00
2016-06-22 02:38:15 +00:00
2016-06-22 02:39:25 +00:00
2016-06-22 02:39:51 +00:00
2016-07-18 16:24:19 +00:00
2016-06-30 08:15:06 +00:00
2016-06-22 02:27:28 +00:00
2016-06-22 02:32:04 +00:00
2016-07-09 00:10:55 +00:00
2016-06-22 02:37:37 +00:00
2016-06-22 02:24:39 +00:00
2016-06-22 02:37:43 +00:00
2016-06-22 06:59:06 +00:00
2016-07-11 15:46:08 +00:00
2016-05-26 15:11:27 +00:00
2016-07-18 17:20:58 +00:00
2016-07-04 19:04:01 +00:00
2016-07-18 20:20:38 +00:00
2016-06-23 21:02:49 +00:00
2016-07-16 02:25:39 +00:00
2016-07-19 01:26:32 +00:00
2016-07-17 12:15:13 +00:00
2016-07-14 11:04:16 +00:00
2016-05-28 12:07:12 +00:00
2016-07-14 03:38:44 +00:00
2016-07-18 16:18:16 +00:00
2016-07-05 19:19:44 +00:00
2016-07-18 21:50:57 +00:00
2016-06-08 20:28:13 +00:00
2016-07-15 23:53:33 +00:00
2016-07-18 23:09:54 +00:00
2016-07-18 17:06:18 +00:00
2016-07-19 02:19:34 +00:00
2016-07-18 21:55:24 +00:00
2016-07-15 22:09:36 +00:00
2016-07-18 03:45:21 +00:00
2016-06-24 00:04:03 +00:00
2016-07-18 14:14:46 +00:00

OpenStack Tracking Repo

zuul gates all of the contained projects in an effective single timeline. This means that OpenStack, across all of the projects, does already have a sequence of combinations that have been explicitly tested, but it's non-trivial to go from a single commit of a particular project to the commits that were tested with it.

Gerrit's submodule tracking feature will update a super project every time a subproject is updated, so the specific sequence created by zuul will be captured by the super project commits.

This repo is intended to be used in a read-only manner. Any commit in this repo will get a collection of commits in the other repos that have explicitly been tested with each other, if that sort of thing is important to you.

Description
Repository tracking all OpenStack repositories as submodules
Readme 199 MiB
Languages
Python 100%