[07:45] <bigjools> any takers https://code.launchpad.net/~julian-edwards/maas/bulk-op-crash-bug-1376023
[07:56] <rvba> bigjools: I'll take it
[10:44] <gmb> rvba, allenap, jtv: For reviewage: https://code.launchpad.net/~gmb/maas/start-and-allocate-bug-1365591/+merge/238130
[10:44]  * gmb -> lunch
[10:45] <allenap> gmb: I’ll have it.
[10:45] <gmb> allenap: Ta
[11:41] <rvba> gmb: I added a comment on https://code.launchpad.net/~gmb/maas/start-and-allocate-bug-1365591/+merge/238130; I think there is something missing in that branch.
[11:47] <rvba> Branch up for review: https://code.launchpad.net/~rvb/maas/explore-intf-bug-1375360/+merge/238139
[11:59] <gmb> rvba: Thanks for the comment on my branch. For clarity: do we definitely want to move to a world where acquisition on start is transparent, even for API calls? I can’t see it doing any harm, I just haven’t seen anything to suggest that (but I can’t think of a reason not to do it)
[12:00] <rvba> gmb: well, if we do it in the UI, it would be weird not to do it in the API.
[12:00] <gmb> rvba: Agreed. I guess I’m assuming that there was a reason for doing things differently in the API, but I guess that’s not really the case…?
[12:03] <rvba> gmb: now that I think about it, you're not really changing an existing behavior, you're in fact adding a shortcut.
[12:03] <gmb> Right.
[12:03] <rvba> gmb: i.e. a shortcut that we can probably decide *not* to add to the API.
[12:05] <gmb> rvba: Right. I’ll leave it as UI for now; we can always fix the API later. Can I have your r= then please?
[12:06] <rvba> gmb: okay
[13:01] <rvba> allenap: care to have a look at https://code.launchpad.net/~rvb/maas/explore-intf-bug-1375360/+merge/238139 again?
[13:06] <allenap> rvba: Bootiful.