- 05 Mar, 2018 1 commit
-
-
Dridi Boukelmoune authored
-
- 02 Mar, 2018 3 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
- 01 Mar, 2018 3 commits
-
-
Poul-Henning Kamp authored
-
Nils Goroll authored
-
Poul-Henning Kamp authored
-
- 28 Feb, 2018 4 commits
-
-
Poul-Henning Kamp authored
(Theory: "stty raw" doesn't clear -echo)
-
Poul-Henning Kamp authored
I came for something else, but one thing led to another... Emit a proper summary at the top, but elide ENUMs to keep it compact. If the entire VCL prototype fits in the header, put it there. else if it fits with ENUMs elided do that or finally resort to just the name + "(...)". If the header didn't hold the full prototype, emit a codeblock with it, and split that in one line per argument if it is too wide for the manual pages. Remove the manual summary from the libvmod_blob docs. otherwise summarize it (ie: elide ENUMs)
-
Poul-Henning Kamp authored
-
Guillaume Quintard authored
-
- 27 Feb, 2018 16 commits
-
-
Dridi Boukelmoune authored
And sync bin/varnishd/Makefile.am to use the same (and more accurate) variable name. Spotted by Reza.
-
Nils Goroll authored
generated VCL synopsis: old: new OBJ = VOID dyn(STRING addr, STRING port) new: new OBJ = dyn(STRING addr, STRING port)
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Spotted by: simon
-
Poul-Henning Kamp authored
-
Nils Goroll authored
Ref: aa8875a4 Ref: c310f04b
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Fixes 2461
-
Poul-Henning Kamp authored
Fixes #2386
-
- 26 Feb, 2018 13 commits
-
-
Poul-Henning Kamp authored
I don't think it matters anywhere else, but future-proofing is good.
-
Nils Goroll authored
-
Nils Goroll authored
Hopefully fixes #2586
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
This should help readability of the code, hopefully. The API remains unchanged. Local variables for vsl_status are called 'r', variables holding a VSLQ_dispatch_f return value are called 'i'
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Nils Goroll authored
-
Nils Goroll authored
-