Permalink
Browse files

Whitespace

  • Loading branch information...
1 parent faae8c1 commit 038b70fdac73bf4d8f6845070b0c48d6788b85a9 @fgsch fgsch committed Dec 10, 2015
Showing with 110 additions and 110 deletions.
  1. +3 −3 Makefile.inc.phk
  2. +4 −4 bin/Makefile.phk
  3. +1 −1 bin/flint.lnt
  4. +1 −1 bin/varnishadm/Makefile.phk
  5. +1 −1 bin/varnishd/Makefile.am
  6. +3 −3 bin/varnishd/flint.lnt
  7. +1 −1 bin/varnishd/vclflint.sh
  8. +4 −4 bin/varnishlog/flint.lnt
  9. +2 −2 bin/varnishncsa/flint.lnt
  10. +4 −4 bin/varnishstat/flint.lnt
  11. +5 −5 bin/varnishtest/flint.lnt
  12. +4 −4 bin/varnishtop/flint.lnt
  13. +4 −4 config.phk
  14. +3 −3 configure.ac
  15. +1 −1 doc/sphinx/Makefile.phk
  16. +1 −1 doc/sphinx/glossary/index.rst
  17. +2 −2 doc/sphinx/installation/bugs.rst
  18. +2 −2 doc/sphinx/installation/help.rst
  19. +1 −1 doc/sphinx/installation/platformnotes.rst
  20. +1 −1 doc/sphinx/phk/autocrap.rst
  21. +1 −1 doc/sphinx/phk/backends.rst
  22. +1 −1 doc/sphinx/phk/barriers.rst
  23. +1 −1 doc/sphinx/phk/gzip.rst
  24. +1 −1 doc/sphinx/phk/http20.rst
  25. +1 −1 doc/sphinx/phk/platforms.rst
  26. +1 −1 doc/sphinx/phk/spdy.rst
  27. +1 −1 doc/sphinx/phk/three-zero.rst
  28. +3 −3 doc/sphinx/phk/wanton_destruction.rst
  29. +2 −2 doc/sphinx/tutorial/backend_servers.rst
  30. +2 −2 doc/sphinx/tutorial/starting_varnish.rst
  31. +2 −2 doc/sphinx/users-guide/command-line.rst
  32. +1 −1 doc/sphinx/users-guide/compression.rst
  33. +13 −13 doc/sphinx/users-guide/devicedetection.rst
  34. +5 −5 doc/sphinx/users-guide/esi.rst
  35. +1 −1 doc/sphinx/users-guide/index.rst
  36. +1 −1 doc/sphinx/users-guide/intro.rst
  37. +2 −2 doc/sphinx/users-guide/operation-logging.rst
  38. +1 −1 doc/sphinx/users-guide/params.rst
  39. +7 −7 doc/sphinx/users-guide/vcl-actions.rst
  40. +3 −3 doc/sphinx/users-guide/vcl-example-acls.rst
  41. +1 −1 doc/sphinx/users-guide/vcl-example-manipulating-headers.rst
  42. +1 −1 doc/sphinx/users-guide/vcl-inline-c.rst
  43. +1 −1 doc/sphinx/users-guide/vcl-variables.rst
  44. +1 −1 include/Makefile.am
  45. +1 −1 lib/Makefile.phk
  46. +2 −2 lib/libvarnish/flint.lnt
  47. +1 −1 lib/libvarnishapi/libvarnishapi.map
  48. +1 −1 lib/libvcc/flint.lnt
  49. +2 −2 lib/libvmod_std/vmod.vcc
  50. +1 −1 varnish.m4
View
@@ -1,6 +1,6 @@
.PHONY: default
-default: all
+default: all
WARNS ?= 1
@@ -39,7 +39,7 @@ LIB_READLINE = ${CFG_LINEDISC}
#######################################################################
ifdef USE_THREADS
CFLAGS += -pthread -D_THREAD_SAFE -g -O2
-PROG_LDFLAGS += -pthread -D_THREAD_SAFE -g -O2
+PROG_LDFLAGS += -pthread -D_THREAD_SAFE -g -O2
endif
ifdef USE_DLOPEN
@@ -164,7 +164,7 @@ ifeq ($(TGT), all)
include _.deplib
endif
-$(LIBNAME).a: $(LIB_OBJ)
+$(LIBNAME).a: $(LIB_OBJ)
$(AR) -rc $(LIBNAME).a $^
ranlib $(LIBNAME).a
View
@@ -1,10 +1,10 @@
-SUBDIRS += varnishadm
-SUBDIRS += varnishd
+SUBDIRS += varnishadm
+SUBDIRS += varnishd
SUBDIRS += varnishlog
SUBDIRS += varnishncsa
-SUBDIRS += varnishtest
+SUBDIRS += varnishtest
SUBDIRS += varnishstat
-SUBDIRS += varnishhist
+SUBDIRS += varnishhist
SUBDIRS += varnishtop
TOPDIR = $(CURDIR)/..
View
@@ -35,7 +35,7 @@
-elib(659) // no tokens after struct def.
-elib(123) // macro def. with arg at, (just warn)
--emacro(702, WEXITSTATUS) // signed shift right
+-emacro(702, WEXITSTATUS) // signed shift right
-e786 // String concatenation within initializer
-e726 // Extraneous comma ignored
@@ -4,7 +4,7 @@ LD_ADD += ${LIB_VARNISHAPI}
LD_ADD += ${LIB_VARNISH}
LD_ADD += ${LIB_PCRE}
LD_ADD += ${LIB_READLINE}
-LD_ADD += -lm
+LD_ADD += -lm
RST_MAN += $(TOPDIR)/doc/sphinx/reference/varnishadm.rst
@@ -97,7 +97,7 @@ varnishd_SOURCES = \
waiter/cache_waiter_epoll.c \
waiter/cache_waiter_kqueue.c \
waiter/cache_waiter_poll.c \
- waiter/cache_waiter_ports.c
+ waiter/cache_waiter_ports.c
noinst_HEADERS = \
builtin_vcl.h \
@@ -118,9 +118,9 @@
-e455 // thread lock
-e458 // unprotected read
-e728 // Symbol ... not explicitly initialized
--e716 // while(1) ...
--e785 // Too few initializers for aggregate
--e850 // for loop index variable '___' whose type category is '___'
+-e716 // while(1) ...
+-e785 // Too few initializers for aggregate
+-e850 // for loop index variable '___' whose type category is '___'
// is modified in body of the for loop that began at '___'
@@ -10,4 +10,4 @@ else
echo "usage!" 1>&2
fi
-flexelint vclflint.lnt /tmp/_.c
+flexelint vclflint.lnt /tmp/_.c
@@ -3,11 +3,11 @@
-e747 // 16 Info 747 Significant prototype coercion (___) ___ to ___
-e763 // Redundant declaration for symbol '...' previously declared
--e716 // while(1) ...
+-e716 // while(1) ...
--e457 // unprotected write access
--e459 // unprotected access
--e458 // unprotected access
+-e457 // unprotected write access
+-e459 // unprotected access
+-e458 // unprotected access
-e732 // Loss of sign (arg. no. 2) (int to unsigned
-e737 // [45] Loss of sign in promotion from int to unsigned
@@ -4,8 +4,8 @@
-e763 // Redundant declaration for symbol '...' previously declared
-e726 // Extraneous comma ignored
-e728 // Symbol ... not explicitly initialized
--e716 // while(1) ...
--e785 // Too few initializers for aggregate
+-e716 // while(1) ...
+-e785 // Too few initializers for aggregate
-e786 // String concatenation within initializer
// cache_center.c
@@ -7,11 +7,11 @@
-e747 // 16 Info 747 Significant prototype coercion (___) ___ to ___
-e763 // Redundant declaration for symbol '...' previously declared
--e716 // while(1) ...
+-e716 // while(1) ...
--e457 // unprotected write access
--e459 // unprotected access
--e458 // unprotected access
+-e457 // unprotected write access
+-e459 // unprotected access
+-e458 // unprotected access
-e732 // Loss of sign (arg. no. 2) (int to unsigned
-e737 // [45] Loss of sign in promotion from int to unsigned
@@ -16,12 +16,12 @@
-e679 // Suspicious Truncation in arithmetic expression combining with pointer
-e763 // Redundant declaration for symbol '...' previously declared
--e716 // while(1) ...
+-e716 // while(1) ...
--e457 // unprotected write access
--e459 // unprotected access
--e458 // unprotected access
-//
+-e457 // unprotected write access
+-e459 // unprotected access
+-e458 // unprotected access
+//
-e732 // Loss of sign (arg. no. 2) (int to unsigned
-e737 // [45] Loss of sign in promotion from int to unsigned
-e713 // Loss of precision (assignment) (unsigned long long to long long)
@@ -3,11 +3,11 @@
-e747 // 16 Info 747 Significant prototype coercion (___) ___ to ___
-e763 // Redundant declaration for symbol '...' previously declared
--e716 // while(1) ...
+-e716 // while(1) ...
--e457 // unprotected write access
--e459 // unprotected access
--e458 // unprotected access
+-e457 // unprotected write access
+-e459 // unprotected access
+-e458 // unprotected access
-e732 // Loss of sign (arg. no. 2) (int to unsigned
-e737 // [45] Loss of sign in promotion from int to unsigned
View
@@ -72,7 +72,7 @@ if true ; then
sys/mount.h \
sys/statvfs.h \
sys/vfs.h \
- umem.h
+ umem.h
do
if [ -f /usr/include/$i ] ; then
n=`echo $i | tr '[a-z/.]' '[A-Z__]'`
@@ -109,7 +109,7 @@ fi
VCSF=include/vcs_version.h
VMAV=include/vmod_abi.h
-if [ -d ./.git ] ; then
+if [ -d ./.git ] ; then
V=`git show -s --pretty=format:%h`
B=`git rev-parse --abbrev-ref HEAD`
else
@@ -147,7 +147,7 @@ fi
ask_compiler() {
a=`echo "$2" |
${CC-cc} -E - -DWARNS=${WARNS-1} |
- sed -e '/^#/d' -e '/^$/d' -e 's/"//g' -e 's/~/"/g' `
+ sed -e '/^#/d' -e '/^$/d' -e 's/"//g' -e 's/~/"/g' `
echo "$1='" $a "'" >> _.cache
}
@@ -302,5 +302,5 @@ exit 0
# HAVE_LIBUMEM -
# USE_PCRE_JIT -
# _FILE_OFFSET_BITS -
-#
+#
# #echo 'CF_CFLAGS="-Wall"'
View
@@ -179,7 +179,7 @@ AC_CHECK_HEADERS([edit/readline/readline.h],
[AC_DEFINE([HAVE_LIBEDIT], [1], [Define if we have libedit])
LIBEDIT_LIBS="-ledit"],
- [PKG_CHECK_MODULES([LIBEDIT], [libedit],
+ [PKG_CHECK_MODULES([LIBEDIT], [libedit],
# having the module does not imply having the header
[AC_CHECK_HEADERS([editline/readline.h],
[AC_DEFINE([HAVE_LIBEDIT], [1], [Define if we have libedit])],
@@ -275,7 +275,7 @@ AC_CACHE_CHECK([whether we have support for visibility attributes],
if test "$ac_cv_have_viz" = no; then
libvgz_extra_cflags="-DNO_VIZ"
AC_SUBST(libvgz_extra_cflags)
-fi
+fi
CFLAGS="${save_CFLAGS}"
# Use jemalloc on Linux
@@ -334,7 +334,7 @@ AC_SYS_LARGEFILE
save_LIBS="${LIBS}"
LIBS="${LIBS} ${RT_LIBS}"
AC_CHECK_FUNCS([clock_gettime])
-AC_CHECK_FUNCS([gethrtime])
+AC_CHECK_FUNCS([gethrtime])
LIBS="${save_LIBS}"
# --enable-kqueue
@@ -189,7 +189,7 @@ EXTRA_DIST = \
include/varnishhist_options.rst \
include/varnishhist_synopsis.rst \
reference/vmod_std.generated.rst \
- reference/vmod_directors.generated.rst
+ reference/vmod_directors.generated.rst
dist-hook:
@@ -4,7 +4,7 @@
Varnish Glossary
================
-.. glossary::
+.. glossary::
:sorted:
..
@@ -19,7 +19,7 @@ do not have a way to simulate high levels of real-life web-traffic,
so telling us to "have 10.000 clients hit at once" does not really
allow us to reproduce.
-To report a bug please follow the suggested procedure described in the "Trouble Tickets"
+To report a bug please follow the suggested procedure described in the "Trouble Tickets"
section of the documentation (above).
Roughly we categorize bugs in to three kinds of bugs (described below) with Varnish. The information
@@ -119,7 +119,7 @@ furiously on some futile condition.
Commands like ``top -H`` or ``ps -Haxlw`` or ``ps -efH`` should be
able to figure that out.
-.. XXX:Maybe a short description of what valuable information the various commands above generates? /benc
+.. XXX:Maybe a short description of what valuable information the various commands above generates? /benc
If one or more threads are spinning, use ``strace`` or ``ktrace`` or ``truss``
@@ -8,7 +8,7 @@ this process as much as possible.
But before you grab hold of us, spend a moment composing your thoughts and
formulate your question. From our perspective there is nothing as pointless as simply telling
-us "Varnish does not work for me" with no further information. This does not give us any relevant information to use when trying to figure out whats wrong.
+us "Varnish does not work for me" with no further information. This does not give us any relevant information to use when trying to figure out whats wrong.
And before you even do that, do a couple of searches to see if your
question is already answered, if it has been, you will get your answer
@@ -78,7 +78,7 @@ bug in Varnish. Ask on IRC first if you are in doubt.
The reason for this policy, is to avoid bugs being drowned in a
pile of other `issues`, feature suggestions for future releases, and double postings of calls for help
-from people who forgot to check back on already opened Tickets.
+from people who forgot to check back on already opened Tickets.
.. XXX: Not sure what you want with the last sentence above. benc
@@ -13,7 +13,7 @@ On RHEL6 Transparent Hugepage kernel support is enabled by default.
This is known to cause sporadic crashes of Varnish.
It is recommended to disable transparent hugepages on affected systems. This
-can be done with
+can be done with
``echo "never" > /sys/kernel/mm/redhat_transparent_hugepage/enabled`` (runtime) and changes to
`/etc/sysctl.conf` (persisted.)
@@ -47,7 +47,7 @@ right before you can even think about compiling the source code.
Second, it doesn't actually work, you still have to do the hard work
and figure out the right way to explain to the autocrap tools what
-you are trying to do and how to do it, only you have to do so in
+you are trying to do and how to do it, only you have to do so in
a language which is used to produce M4 macro invocations etc. etc.
In the meantime, the UNIX diversity has shrunk from 50+ significantly
@@ -52,7 +52,7 @@ VCLs where backend "b1" points at two different physical machines,
for instance when we migrate or upgrade the backend.
The identity of the state than can be shared is therefore the triplet:
- {VCL-name, IPv4+port, IPv6+port}
+ {VCL-name, IPv4+port, IPv6+port}
No Information without Representation
=====================================
@@ -48,7 +48,7 @@ barriers between the various components::
The really Important Barrier
============================
-The central actor in Varnish is the Manager process, "MGR", which is the
+The central actor in Varnish is the Manager process, "MGR", which is the
process the administrator "(ADMIN)" starts to get web-cache service.
Having been there myself, I do not subscribe to the "I feel cool and important
@@ -47,7 +47,7 @@ always set to:
Accept-Encoding: gzip
-Even if this particular client does not support
+Even if this particular client does not support
To always entice the backend into sending us gzip'ed content.
@@ -257,7 +257,7 @@ and repeat markers, rather than throwing everything after deflate
and hope for a miracle.
I think this protocol is the best basis to start from, but like
-the other two, it has a long way to go, before it can truly
+the other two, it has a long way to go, before it can truly
earn the name HTTP/2.0.
@@ -39,7 +39,7 @@ We care about these platforms because our users use them and
because they deliver a lot of bang for the buck with Varnish.
These platforms are in our "tinderbox" tests, we use them ourselves
-and they pass all regression tests all the time.
+and they pass all regression tests all the time.
Platform specific bug reports gets acted on.
*FreeBSD*
@@ -61,7 +61,7 @@ Treaty and the convention about chemical and biological weapons.)
So my insight about Varnish, that it has to become a socket-wrench-like
toolchest for doing things with HTTP traffic, will probably elicit a lot
-of "duh!" reactions, until people, including me, understand the
+of "duh!" reactions, until people, including me, understand the
ramifications more fully.
Things you cannot do with Varnish today
@@ -53,7 +53,7 @@ shows a nice trend on Google and #varnish confuses the heck out of
teenage girls and wood workers on Twitter, so clearly I am doing
something right.
-I still worry about the `The Fraud Police
+I still worry about the `The Fraud Police
<http://www.theshadowbox.net/forum/index.php?topic=18041.0>`_ though,
"I have no idea what I'm doing, and I totally make shit up as I go
along." is a disturbingly precise summary of how I feel about my
@@ -24,7 +24,7 @@ rebuild it, to become the house we want now.
For one thing, doing major surgery on a house while you live in it
is double-minus-fun and it always slows the rebuild project down
-when you have to keep at least one toilet working and sanitary and
+when you have to keep at least one toilet working and sanitary and
be able to cook and sleep on the building site.
So we'll be building a new house on a plot of land on the other
@@ -40,7 +40,7 @@ Using a major piece of software, is like moving into a house: You
need to adapt your life and the house or the software to each other,
since nothing is ever quite perfect, there will be limitations.
-And those limitations affect how you think: If you live in a
+And those limitations affect how you think: If you live in a
2 bedroom apartment, you won't even be considering inviting 80
guests to a party.
@@ -55,7 +55,7 @@ the next couple of years, it'll be called Varnish V4 and that means
that you will have to decide who gets which room and where to store
the towels and grandmothers old china, all over again.
-I'm sure you'll hate me for it, "Why do we have to move ?", "It
+I'm sure you'll hate me for it, "Why do we have to move ?", "It
really wasn't that bad after all" and so on and so forth.
But if I do my job right, that will soon turn into "Ohh, that's
pretty neat, I always wanted one of those..." and "Hey... Watch me
Oops, something went wrong.

0 comments on commit 038b70f

Please sign in to comment.