are willing to evict per storage allocation attempt.

Previously this was hardcoded at 50, make it 10 instead.

The ABI we give vmods consist of the Varnish version number and the
git commit ID meaning we can break ABI at will.

Output a warning if we can't determine git commit ID

data, the thread would go into a spin.

Fixes	#942

Found & Fixed by:	Martin

Fixes	#978

Found & Fixed by:	Martin

Fixes	#979

	we transform (gzip/gunzip)
	we stream and backend didn't send c-l.

Fixes	#980

Testcase by:	Martin

non-busy.  Not sure what I thought when I changed it last, but it
was clearly not smart thinking.

Spotted by:	Martin
Test case by:	Martin

Fixes	#963

If the first (policy-chosen) backend fails to get us a connection,
retry a random backend (still according to their weight) until
retries are exhausted.

Kristian sent a proof of concept patch, I just cleaned it up and made
it compile.

Thanks to:	Kristian

Fixes	#977

32 bit systems.

Spotted by:	Kristian

didn't get it rigth the first time.
Thanks to scoof for pointing it out.

Explained the semantics quickly so people understand why not all objects survive a crash

response code stuff and fully incorporate the fact that they are both
16 unsigned now.

No functional changes.

Ironically, this does NOT fix #971 (see if you can handle this, trac).
(WIP)

the silo into VM.  If this fails or we get garbage, the silo will
be cleared.

Fixes	#962

expect:

Clamp rather than overflow on child indexes when we get to the
end of the UINT_MAX items we can support.

Found by adding a lot of asserts and brute force testing, both
of which I have left in.

Fixes       #967

May also be relevant to #827

end of the UINT_MAX items we can support.

Found by adding a lot of asserts and brute force testing, both
of which I have left in.

Fixes 	#967

May also be relevant to #827

also have the 206/range handling.

Instead of building the 304 response from scratch, dumb down the
200 response accordingly.

This implement the policy consideration of #970 led to.