- 25 Mar, 2014 2 commits
-
-
Poul-Henning Kamp authored
by lru->mtx. Spotted by: Martin
-
Poul-Henning Kamp authored
-
- 24 Mar, 2014 12 commits
-
-
Poul-Henning Kamp authored
Remove a debugging message.
-
Dag Haavi Finstad authored
Test case by: Federico G. Schwindt Fixes: #1417
-
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
we close from our side with the new SC_RESP_CLOSE status.
-
Poul-Henning Kamp authored
Spotted by: martin
-
Poul-Henning Kamp authored
Now that we have a proper purge-mechanism, all the magic to set obj.{ttl,grace,keep} in vcl_hit{} can go away.
-
- 22 Mar, 2014 1 commit
-
-
Lasse Karstensen authored
The builtin VCL supports this now. Since so many noticed this missing in 3.0, I think it should be mentioned.
-
- 21 Mar, 2014 8 commits
-
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Lasse Karstensen authored
Generated RST file should live in include/ like the others, not in reference/. Try to make the code slightly more readable through a descriptive variable name for the file handle.
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
I don't have Python 3.1, but I do have Python 3.3.5 which should suffice.
-
Tollef Fog Heen authored
-
- 20 Mar, 2014 17 commits
-
-
Tollef Fog Heen authored
-
Tollef Fog Heen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-
Lasse Karstensen authored
We include these autogenerated files directly where they are needed. Let the main sphinx process ignore them, so it doesn't complain that they're not referenced anywhere.
-
Lasse Karstensen authored
-
Lasse Karstensen authored
Try to document our conventions when it comes to commands, paths, tool names and similar. Also write some formatting rules for maintainers, like wrapping at 80 characters and avoiding tabs. I'm happy to discuss changing these if someone feels strongly about anything, the main point is just to make it easier to read though being consequent about it throughout the manual.
-
Lasse Karstensen authored
-
Lasse Karstensen authored
-