In general I would not advice doing this, but if you are strictly
on a fortified localhost or localnet I can see the point.

Fixes	#893

draconian about error handling and debugging.

Properly handle two src= attributes in an esi:include tag (ignore
the entire tag, log the error)

Deal with clients which close the connection half-way through an
ESI delivery.

Make it possible to specify the period varnishtop should integrate
numbers over.  This makes it easier to figure out per time period
stats.

Fixes	#887

-o is needed for matching on tag/regex, the documentation did not make
 this clear.

The varnish tools need some private libraries and find then via rpath,
so avoid stripping the rpath when building RPMs

a buf to be flushed to WRW.

Having printw() take a "char*" rather than "const char*" as fmt argument
feels sooo 1980 to me...

Generate varnish-cli.7 and clean up the generated man pages on
maintainer-clean

to the VGZ_STUCK indication.

Hopefully helps with #869

this looks like it helps PPC64 platform.

too large to serve in one bite, so chop it down until we reach
fetch_chunksize before we start LRU flushing to make space for it.

Fixes #880

Fixes:	878

Solved by:	tmagnien

clarity.

thread workspace, to make sure they are not overwritten before they
make it out the wire.