Commits
- Commit:
fba809b5c775fd4d3c28a012259ee3b1908d4e40
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag 1.7.3
bump version number
- Commit:
2bb1776bacc96357fc182ef396508fe71816e0b0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
keep the openssl key generation example under 80 columns
- Commit:
301e039d24172a5e15bed60701bf279798d28621
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
gmid.1: some spelling, grammar and crosslinks
- Commit:
e308526cf63d7cbbabaa4bf93bae45a27fb58d4b
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
gmid.1: provide certificate generation example
- Commit:
e58a447a28a416ee719a9e457bfc8160a9b0e771
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
gmid.1: document logging
- Commit:
af5f9b271e852c641ff6c1d226e42d98f4182f25
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use \e instead of \\ as a mean to escape \
Just read in a mail from Ingo to tech@
> Using \\ outside macro definitions (i.e., outside the bodies of roff(7)
> .de and similar requests) is almost always wrong even in low-level roff
> code, and \\ must never be used in manual pages.
- Commit:
8068d2ff33992fcaf0e5f38bc7b3d86789e7e92e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7.1
This version includes two bugfixes:
- use ${MAKE} to recursively call make
- fix the misleading example in the man page: macros name may not be
reserved words
Both bugs found and fixed by Anna “CyberTailor”, thanks!
- Commit:
ad15003be8fc1422b52600f1d5c6b6875e46cad7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
align
- Commit:
2d06ae62aeb4c107a1c8fd04f23aa81b5b93fe3f
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
fix misleading example in man page
> Macros names may not be reserved words
- Commit:
b79b2d811b7775f6be71f7248c3cc498a6115bb0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7
- Commit:
528f37cd2dbed6a7906e3adb96c12f44acba919d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync macro usage and mention the `include' keyword
- Commit:
3d132b283345475921bf9cf1e8d77e56ede2edf3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
`param' is forbidden inside `location's too
and while there sort the list of disallowed rules.
- Commit:
2b520ad595f4ac7d438ace3abf2a0e2dd2fb78b5
- From:
- Omar Polo <op@omarpolo.com>
- Date:
misc improvements to the manual
- Commit:
efacb859a7ebc65cff1b51cff04cdc2aea3135e1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
change (again) the env/param separator: use '='
Given that env/param are new features of this release, no support for
the "old" syntax is needed.
- Commit:
762b9b991f373e5077d7e49396af62a34fa1c1ff
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add => in env/param and `port' between hostname and port for fastcgi
In the same spite of the last commit, add the missing separators
between strings to avoid the auto-concat pitfalls. `=>' is used to
separate between `env' and `param' arguments, while for `fastcgi' the
keyword `port' is required between the hostname/ip address and the
port (if provided).
Since `env', `param' and `fastcgi' are all new stuff, there's no need
to keep compatibility.