Commits
- Commit:
b79b2d811b7775f6be71f7248c3cc498a6115bb0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7
- Commit:
f361f7997917a42a7b377d2764c5fb7467cccb62
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move version number to configure script
- Commit:
a82d4dfa25d30d3c512bd1fc15821186bf4d35c4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
provide a fallback value for SKIP_RUNTIME_TESTS
some [ implementation will warn about "bad number"
- Commit:
9f075bd689f0ca2c362fc1bbde0dbfc316cffeb3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync
- Commit:
391825e3604deef4c9dc3267dc2b6c89fc79958a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move parse_portno to gmid.c
it's used only to parse the -p flag. While there add check_port_num
to check the range for the port.
- Commit:
e3b2a0f8de7210c4d403cf4c30d956c34d8c9353
- From:
- Omar Polo <op@omarpolo.com>
- Date:
missing newline in deprecation notice
- Commit:
1bd706dc4150dbcb42d48b98854e46a78ceda861
- From:
- Omar Polo <op@omarpolo.com>
- Date:
drop unsigned
it causes a cascade of warnings on some architectures. Also, for what
we're doing here, the signed/unsigned property isn't important.
- Commit:
528f37cd2dbed6a7906e3adb96c12f44acba919d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync macro usage and mention the `include' keyword
- Commit:
67f494057aa3a0a32cc4d948cff2f27ef9de2340
- From:
- Omar Polo <op@omarpolo.com>
- Date:
@-macros, rollback changes to strings and optional semicolons
* expand $-macros as string, only the new @-macros get expanded as-is
* rollback changes to characters allowed in bare strings
* optional semicolons in optnl, useful for readable @-macros
- Commit:
c39be742cf8348232f6a527b19c42f764e80aae0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
parsing: bring lots of goodies from OpenBSD' parse.y
This allows to solve the problem with the \n in the grammar (before
two following macro declaration were treated as invalid. This also
brings in a nice `include' keyword.
- Commit:
a5d822e542a927e88f655842273356225370c11f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo
- Commit:
be52e954c1d54f80485c643663db8e2ffc27510f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync readme.md with sandbox.c
- 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.