(1) Bump version 2.21.1 to 2.22
(2) Add patches/patch-configure.ac (just for convenience)
(3) Try to reduce pkglint/pkglint -Wall  0-7/0-38
(4) Update TODO

Update to 5.8.7.
Changes since 5.8.6:

• bugfix: instabilities when using RFC5424 header fields Thanks to Kaiwang Chen for the patch
• bugfix: imuxsock did truncate part of received message if it did not contain a proper date. The truncation occured because we removed that part of the messages that was expected to be the date. closes: http://bugzilla.adiscon.com/show_bug.cgi?id=295
• bugfix: potential abort after reading invalid X.509 certificate closes: http://bugzilla.adiscon.com/show_bug.cgi?id=290 Thanks to Tomas Heinrich for the patch
• bugfix: stats counter were not properly initialized on creation
• FQDN hostname for multihomed host was not always set to the correct name if multiple aliases existed. Thanks to Tomas Heinreich for the patch.

Update to 6.2.0
---------------------------------------------------------------------------
Version 6.2.0 [v6-stable], 2012-01-09

• bugfix (kind of): removed numerical part from pri-text see v6 compatibility document for reasons
• bugfix: race condition when extracting program name, APPNAME, structured data and PROCID (RFC5424 fields) could lead to invalid characters e.g. in dynamic file names or during forwarding (general malfunction of these fields in templates, mostly under heavy load)
• bugfix: imuxsock did no longer ignore message-provided timestamp, if so configured (the *default*). Lead to no longer sub-second timestamps. closes: http://bugzilla.adiscon.com/show_bug.cgi?id=281
• bugfix: omfile returns fatal error code for things that go really wrong previously, RS_RET_RESUME was returned, which lead to a loop inside the rule engine as omfile could not really recover.
• bugfix: rsyslogd -v always said 64 atomics were not present thanks to mono_matsuko for the patch
• bugfix: potential abort after reading invalid X.509 certificate closes: http://bugzilla.adiscon.com/show_bug.cgi?id=290 Thanks to Tomas Heinrich for the patch
• $Begin, $End, $StrictScoping directives have been removed as v6.4 will provide the same functionality in a far better way. So we do not want to clutter the code. --------------------------------------------------------------------------- Version 6.1.12 [BETA], 2011-09-01
• bugfix/security: off-by-two bug in legacy syslog parser, CVE-2011-3200
• bugfix: mark message processing did not work correctly
• bugfix: potential misadressing in property replacer
• bugfix: memcpy overflow can occur in allowed sender checkig if a name is resolved to IPv4-mapped-on-IPv6 address Found by Ismail D????nmez at suse
• bugfix: The NUL-Byte for the syslogtag was not copied in MsgDup (msg.c)
• bugfix: fixed incorrect state handling for Discard Action (transactions) Note: This caused all messages in a batch to be set to COMMITTED, even if they were discarded. --------------------------------------------------------------------------- Version 6.1.11 [BETA] (rgerhards), 2011-07-11
• systemd support: set stdout/stderr to null - thx to Lennart for the patch
• added support for the ":omusrmsg:" syntax in configuring user messages
• added support for the ":omfile:" syntax in configuring user messages --------------------------------------------------------------------------- Version 6.1.10 [BETA] (rgerhards), 2011-06-22
• bugfix: problems in failover action handling closes: http://bugzilla.adiscon.com/show_bug.cgi?id=270 closes: http://bugzilla.adiscon.com/show_bug.cgi?id=254
• bugfix: mutex was invalidly left unlocked during action processing At least one case where this can occur is during thread shutdown, which may be initiated by lower activity. In most cases, this is quite unlikely to happen. However, if it does, data structures may be corrupted which could lead to fatal failure and segfault. I detected this via a testbench test, not a user report. But I assume that some users may have had unreproducable aborts that were cause by this bug. --------------------------------------------------------------------------- Version 6.1.9 [BETA] (rgerhards), 2011-06-14
• bugfix: problems in failover action handling closes: http://bugzilla.adiscon.com/show_bug.cgi?id=270 closes: http://bugzilla.adiscon.com/show_bug.cgi?id=254
• bugfix: mutex was invalidly left unlocked during action processing At least one case where this can occur is during thread shutdown, which may be initiated by lower activity. In most cases, this is quite unlikely to happen. However, if it does, data structures may be corrupted which could lead to fatal failure and segfault. I detected this via a testbench test, not a user report. But I assume that some users may have had unreproducable aborts that were cause by this bug.
• bugfix/improvement:$WorkDirectory now gracefully handles trailing slashes --------------------------------------------------------------------------- Version 6.1.9 [BETA] (rgerhards), 2011-06-14
• bugfix: memory leak in imtcp & subsystems under some circumstances This leak is tied to error conditions which lead to incorrect cleanup of some data structures. [backport from v6.3]
• bugfix: $ActionFileDefaultTemplate did not work closes: http://bugzilla.adiscon.com/show_bug.cgi?id=262 --------------------------------------------------------------------------- Version 6.1.8 [BETA] (rgerhards), 2011-05-20
• official new beta version (note that in a sense 6.1.7 was already beta, so we may release the first stable v6 earlier than usual)
• new module mmsnmptrapd, a sample message modification module
• import of minor bug fixes from v4 & v5 --------------------------------------------------------------------------- Version 6.1.7 [DEVEL] (rgerhards), 2011-04-15
• added log classification capabilities (via mmnormalize & tags)
• speeded up tcp forwarding by reducing number of API calls this especially speeds up TLS processing
• somewhat improved documentation index
• bugfix: enhanced imudp config processing code disabled due to wrong merge (affected UDP realtime capabilities)
• bugfix (kind of): memory leak with tcp reception epoll handler This was an extremely unlikely leak and, if it happend, quite small. Still it is better to handle this border case.
• bugfix: IPv6-address could not be specified in omrelp this was due to improper parsing of ":" closes: http://bugzilla.adiscon.com/show_bug.cgi?id=250

 Update to 0.3.3.
Changes since 0.3.1:
 * required header file was not installed, resulting in compile error
   closes: http://bugzilla.adiscon.com/show_bug.cgi?id=307
 * added rfc5424 parser (requires libee >= 0.3.2)
 * added "-" to serve as name for filler fields. Value is extracted,
   but no field is written
 * special handling for iptables log via %iptables% parser added
   (currently experimental pending practical verification)
 * normalizer tool on its way to a full-blow stand-alone tool
 * support for annotations added, for the time being see
   http://blog.gerhards.net/2011/11/log-annotation-with-liblognorm.html

 Update to 0.3.2
Changes since 0.3.1
 * API enhancements:
    - added capability to enumerate tags inside a tagbucket
    - added capability to obtain tagbucket for an event
      -> ee_EventGetTagbucket()
    - added capability to add a string value to a field in one call
      -> ee_addStrValueToField()
    - added ee_getTag(), ee_setTags()
 * added additional parser
    - RFC5424Date
 * potentially problematic API change: in earlier versions,
   the function ee_TagbucketHasTag() was errornously name ee_BucketHasTag().
 * This has been corrected, potentially resulting in API incompatibility.
   We have accepted this, because we are at level 0.x AND know that potentially
   no current user has ever used this function, but instead the upper-layer
   equivalents. But if thinks break, you now know why ;)
 * flat tags are no longer encoded in the CEE encoders as CEE does not support
   flat tags. However, this can be turned on via context flags, if desired
 * bugfix: compile problems under Solaris
   closes: http://bugzilla.adiscon.com/show_bug.cgi?id=253
 * bugfix: ee_EventGetTagbucket() always returned -1 (error)