Re: VTest output change

2019-06-19 Thread Poul-Henning Kamp
In message <20190619081053.ga3...@1wt.eu>, Willy Tarreau writes: >On Tue, Jun 18, 2019 at 07:13:51AM +, Poul-Henning Kamp wrote: >> >> In message , Frederic >> Lecaill >> e writes: >> >> >It seems there is no objection ;) >> >> That's what I figured :-) > >Thanks. I also

Re: VTest output change

2019-06-19 Thread Willy Tarreau
On Tue, Jun 18, 2019 at 07:13:51AM +, Poul-Henning Kamp wrote: > > In message , Frederic > Lecaill > e writes: > > >It seems there is no objection ;) > > That's what I figured :-) Thanks. I also found diffs annoying to run because of this. It should indeed be better this way.

Re: VTest output change

2019-06-18 Thread Poul-Henning Kamp
In message , Frederic Lecaill e writes: >It seems there is no objection ;) That's what I figured :-) Pushed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to

Re: VTest output change

2019-06-18 Thread Frederic Lecaille
On 6/17/19 3:19 PM, Poul-Henning Kamp wrote: Hi, Hi Poul-Henning, For reason now obscured by history, VTest has a (relative) timestamp on every line of its output: *** v1 27.4 CLI RX 300 v1 27.4 CLI RX|Cannot set the active VCL cold. ** v1 27.4 CLI 300

VTest output change

2019-06-17 Thread Poul-Henning Kamp
Hi, For reason now obscured by history, VTest has a (relative) timestamp on every line of its output: *** v1 27.4 CLI RX 300 v1 27.4 CLI RX|Cannot set the active VCL cold. ** v1 27.4 CLI 300 ** top 27.4 === varnish v1 -cliok "vcl.state vcl1