*** k0da has quit IRC | 01:34 | |
*** AlexeyAbashkin has joined #openstack-powervm | 04:57 | |
*** efried has quit IRC | 05:29 | |
*** adi_____ has quit IRC | 05:30 | |
*** adi_____ has joined #openstack-powervm | 05:30 | |
*** efried has joined #openstack-powervm | 05:38 | |
*** mujahidali has joined #openstack-powervm | 05:38 | |
*** AlexeyAbashkin has quit IRC | 05:41 | |
*** k0da has joined #openstack-powervm | 06:05 | |
*** efried has quit IRC | 06:11 | |
*** efried has joined #openstack-powervm | 06:11 | |
*** mujahidali has quit IRC | 06:28 | |
*** mujahidali has joined #openstack-powervm | 06:28 | |
*** k0da has quit IRC | 06:48 | |
*** k0da has joined #openstack-powervm | 06:48 | |
*** openstackgerrit has quit IRC | 07:04 | |
*** AlexeyAbashkin has joined #openstack-powervm | 07:56 | |
*** mujahidali has quit IRC | 08:29 | |
*** mujahidali has joined #openstack-powervm | 08:30 | |
*** mujahidali has quit IRC | 11:22 | |
*** edmondsw has joined #openstack-powervm | 12:41 | |
-openstackstatus- NOTICE: logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown. | 12:57 | |
*** ChanServ changes topic to "logs.openstack.org is offline, causing POST_FAILURE results from Zuul. Cause and resolution timeframe currently unknown." | 12:57 | |
*** esberglu has joined #openstack-powervm | 13:07 | |
*** esberglu has quit IRC | 13:14 | |
*** esberglu has joined #openstack-powervm | 13:17 | |
*** ChanServ changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack." | 13:40 | |
-openstackstatus- NOTICE: logs.openstack.org is back on-line. Changes with "POST_FAILURE" job results should be rechecked. | 13:40 | |
*** k0da has quit IRC | 13:59 | |
*** k0da has joined #openstack-powervm | 14:15 | |
*** mujahidali has joined #openstack-powervm | 14:33 | |
*** k0da has quit IRC | 14:47 | |
*** k0da has joined #openstack-powervm | 14:47 | |
*** k0da has quit IRC | 15:07 | |
*** AlexeyAbashkin has quit IRC | 15:40 | |
*** k0da has joined #openstack-powervm | 16:35 | |
edmondsw | efried if I wanted to backport something to multiple releases, I would generally backport to the newest first, and then from that to the next, etc. | 16:37 |
---|---|---|
edmondsw | does it have to happen that way, or could someone backport directly from master to each release? | 16:37 |
edmondsw | I mean they could... but what would the consequences be?? | 16:38 |
*** esberglu has quit IRC | 16:59 | |
*** esberglu has joined #openstack-powervm | 17:00 | |
*** esberglu has quit IRC | 17:04 | |
*** edmondsw has quit IRC | 17:13 | |
*** edmondsw has joined #openstack-powervm | 17:18 | |
*** esberglu has joined #openstack-powervm | 17:31 | |
efried | edmondsw: Consequences are only the comment at the bottom of the commit message (cherry picked from commit XXXX) which you could add manually if you wanted. | 17:35 |
efried | edmondsw: Typically those comments get accumulated with each stepwise backport, so the -N backport has N such comments. | 17:36 |
edmondsw | yep, that's what I was thinking, but wanted to make sure I wasn't missing anything | 17:37 |
edmondsw | tx | 17:37 |
*** openstackgerrit has joined #openstack-powervm | 17:49 | |
openstackgerrit | Merged openstack/nova-powervm master: iSCSI volume detach with no UDID https://review.openstack.org/576034 | 17:49 |
*** mujahidali has quit IRC | 17:59 | |
*** edmondsw has quit IRC | 18:03 | |
*** k0da has quit IRC | 18:09 | |
*** k0da has joined #openstack-powervm | 18:24 | |
*** edmondsw has joined #openstack-powervm | 18:31 | |
*** edmondsw has quit IRC | 22:30 | |
*** edmondsw has joined #openstack-powervm | 22:31 | |
*** k0da has quit IRC | 22:31 | |
*** edmondsw has quit IRC | 22:35 | |
*** esberglu has quit IRC | 23:34 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!