Re: [PATCH 2/3] qga: Add optional `merge-output` flag to guest-exec qapi

Hi On Tue, Feb 28, 2023 at 5:15 AM Daniel Xu wrote: > > Hi, > > On Mon, Feb 27, 2023, at 1:22 AM, Marc-André Lureau wrote: > > Hi > > > > On Fri, Feb 24, 2023 at 8:31 AM Daniel Xu wrote: > >> > >> Currently, the captured output (via `capture-output`) is segregated into > >> separate

Re: [PATCH 2/3] qga: Add optional `merge-output` flag to guest-exec qapi

Hi, On Mon, Feb 27, 2023, at 1:22 AM, Marc-André Lureau wrote: > Hi > > On Fri, Feb 24, 2023 at 8:31 AM Daniel Xu wrote: >> >> Currently, the captured output (via `capture-output`) is segregated into >> separate GuestExecStatus fields (`out-data` and `err-data`). This means >> that downstream

Re: [PATCH 2/3] qga: Add optional `merge-output` flag to guest-exec qapi

Hi On Fri, Feb 24, 2023 at 8:31 AM Daniel Xu wrote: > > Currently, the 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

[PATCH 2/3] qga: Add optional `merge-output` flag to guest-exec qapi

Currently, the 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