Dan Allan
Dan Allan
Well said.
Right. In the earliest draft of this PR I just dropped the reference to the thread (“put black tape over the red warning light”) to prompt discussion on the question...
That would be great!
This needs a rebase, and tests. (Note to self.) Otherwise it seems there is consensus for merging.
Thanks for pushing on this @prjemian .
> Will there be troubles with `.put()`? No, this is semi-internal. It operates one layer below Status objects so it should not have anything to do with "poison pill".
Thanks @xiaoqiangwang. This is a very sensible suggestion.
With a little more time to think, let me respond more thoroughly. Acquire start/stop is already handled by the [Triggerable protocol](https://blueskyproject.io/bluesky/hardware.html#bluesky.protocols.Triggerable), which initiates "start" and returns [status object](https://blueskyproject.io/ophyd/explanations/status.html) that provides...
@kgofron `git revert` _adds_ a commit, leaving a record that some previous commit has been un-done. Someone a merge commit ended in here too. @tacaswell wants the original two commits...
@kgofron I suspect you did the merge on GH and so you need to either pull that merge commit you created on the remote first or else do plain `--force`....