On 2022-10-14 06:49 pm, Jan Ekström wrote:
On Tue, Sep 27, 2022 at 7:41 AM Gyan Doshi wrote:
The current adjustment of input start times just adjusts the tsoffset.
And it does so, by resetting the tsoffset to nullify the new start time.
This leads to breakage of -copyts, ignoring of user_ts_o
On Tue, Sep 27, 2022 at 7:41 AM Gyan Doshi wrote:
>
> The current adjustment of input start times just adjusts the tsoffset.
> And it does so, by resetting the tsoffset to nullify the new start time.
> This leads to breakage of -copyts, ignoring of user_ts_offset, breaking
> of -isync as well as b
On 2022-10-12 09:50 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2022-09-27 06:40:56)
The current adjustment of input start times just adjusts the tsoffset.
And it does so, by resetting the tsoffset to nullify the new start time.
This leads to breakage of -copyts, ignoring of user_ts_offset,
Quoting Gyan Doshi (2022-09-27 06:40:56)
> The current adjustment of input start times just adjusts the tsoffset.
> And it does so, by resetting the tsoffset to nullify the new start time.
> This leads to breakage of -copyts, ignoring of user_ts_offset, breaking
On 2022-10-04 02:41 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2022-10-02 21:46:59)
On 2022-09-27 10:10 am, Gyan Doshi wrote:
The current adjustment of input start times just adjusts the tsoffset.
And it does so, by resetting the tsoffset to nullify the new start time.
This leads to break