Hi Konstantin,
On Mon, Apr 3, 2023, at 8:56 AM, Konstantin Kostiuk wrote:
> Hi Daniel,
>
> I will merge this series after the 8.0 release.
>
> Best Regards,
> Konstantin Kostiuk.
>
Sorry to bug again, but 8.0 is out now right? Does this need a rebase
or is it good to go?
Thanks,
Daniel
[...]
Hi Daniel,
I will merge this series after the 8.0 release.
Best Regards,
Konstantin Kostiuk.
On Fri, Mar 31, 2023 at 11:24 PM Daniel Xu wrote:
> Hi Daniel,
>
> On Thu, Mar 23, 2023, at 3:26 AM, Daniel P. Berrangé wrote:
> > On Wed, Mar 22, 2023 at 06:19:27PM -0600, Daniel Xu wrote:
> >>
Hi Daniel,
On Thu, Mar 23, 2023, at 3:26 AM, Daniel P. Berrangé wrote:
> On Wed, Mar 22, 2023 at 06:19:27PM -0600, Daniel Xu wrote:
>> Currently, any captured output (via `capture-output`) is segregated into
>> separate GuestExecStatus fields (`out-data` and `err-data`). This means
>> that
On Wed, Mar 22, 2023 at 06:19:27PM -0600, Daniel Xu wrote:
> Currently, any captured output (via `capture-output`) is segregated into
> separate GuestExecStatus fields (`out-data` and `err-data`). This means
> that downstream consumers have no way to reassemble the captured data
> back into the
Currently, any captured output (via `capture-output`) is segregated into
separate GuestExecStatus fields (`out-data` and `err-data`). This means
that downstream consumers have no way to reassemble the captured data
back into the original stream.
This is relevant for chatty and semi-interactive
